PR #110991 pull-kubernetes-e2e-capz-windows-containerd #1591188080616804352
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | thockin: Svc typenames star traffic policy type |
| Result | SUCCESS |
| Tests | 4 failed / 6 succeeded |
| Started | |
| Elapsed | 1h5m |
| Revision | b30b876ad14a079bf3430eec3f0259d0a56f6e16 |
| Refs |
110991 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
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\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
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\]$'
test/e2e/e2e.go:249
k8s.io/kubernetes/test/e2e.setupSuite()
test/e2e/e2e.go:249 +0x4de
k8s.io/kubernetes/test/e2e.glob..func1()
test/e2e/e2e.go:81 +0x8f
reflect.Value.call({0x66064e0?, 0x77d68f0?, 0x0?}, {0x74fe488, 0x4}, {0xc000bddf20, 0x0, 0x0?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x66064e0?, 0x77d68f0?, 0x0?}, {0xc000bddf20?, 0x0?, 0x0?})
/usr/local/go/src/reflect/value.go:368 +0xbc
[SynchronizedBeforeSuite] TOP-LEVEL
test/e2e/e2e.go:77
Nov 11 22:40:00.806: INFO: >>> kubeConfig: /tmp/kubeconfig
Nov 11 22:40:00.811: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Nov 11 22:40:01.288: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Nov 11 22:40:01.679: INFO: The status of Pod calico-node-windows-b7mdr is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:01.679: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:01.679: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:01.679: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:01.679: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Nov 11 22:40:01.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:01.679: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:01.679: INFO: calico-node-windows-b7mdr capz-conf-tg7l2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:08 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:58 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:58 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:29 +0000 UTC }]
Nov 11 22:40:01.679: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:01.679: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:01.679: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:01.679: INFO:
Nov 11 22:40:04.060: INFO: The status of Pod calico-node-windows-b7mdr is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:04.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:04.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:04.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:04.060: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Nov 11 22:40:04.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:04.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:04.060: INFO: calico-node-windows-b7mdr capz-conf-tg7l2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:08 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:58 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:58 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:29 +0000 UTC }]
Nov 11 22:40:04.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:04.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:04.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:04.060: INFO:
Nov 11 22:40:06.098: INFO: The status of Pod calico-node-windows-b7mdr is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:06.099: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:06.099: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:06.099: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:06.099: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Nov 11 22:40:06.099: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:06.099: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:06.099: INFO: calico-node-windows-b7mdr capz-conf-tg7l2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:08 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:58 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:58 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:29 +0000 UTC }]
Nov 11 22:40:06.099: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:06.099: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:06.099: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:06.099: INFO:
Nov 11 22:40:08.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:08.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:08.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:08.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Nov 11 22:40:08.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:08.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:08.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:08.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:08.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:08.064: INFO:
Nov 11 22:40:10.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:10.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:10.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:10.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Nov 11 22:40:10.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:10.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:10.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:10.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:10.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:10.066: INFO:
Nov 11 22:40:12.057: INFO: The status of Pod calico-node-windows-h6hwl is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:12.057: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:12.057: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:12.057: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:12.057: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Nov 11 22:40:12.057: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:12.057: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:12.057: INFO: calico-node-windows-h6hwl capz-conf-r49vt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:40:11 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:40:11 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:46 +0000 UTC }]
Nov 11 22:40:12.057: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:12.057: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:12.057: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:12.057: INFO:
Nov 11 22:40:14.059: INFO: The status of Pod calico-node-windows-h6hwl is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:14.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:14.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:14.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:14.059: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Nov 11 22:40:14.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:14.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:14.059: INFO: calico-node-windows-h6hwl capz-conf-r49vt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:40:11 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:40:11 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:46 +0000 UTC }]
Nov 11 22:40:14.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:14.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:14.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:14.059: INFO:
Nov 11 22:40:16.059: INFO: The status of Pod calico-node-windows-h6hwl is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:16.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:16.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:16.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:16.059: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Nov 11 22:40:16.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:16.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:16.059: INFO: calico-node-windows-h6hwl capz-conf-r49vt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:40:11 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:40:11 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:46 +0000 UTC }]
Nov 11 22:40:16.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:16.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:16.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:16.059: INFO:
Nov 11 22:40:18.065: INFO: The status of Pod calico-node-windows-h6hwl is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:18.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:18.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:18.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:18.065: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Nov 11 22:40:18.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:18.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:18.065: INFO: calico-node-windows-h6hwl capz-conf-r49vt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:24 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:40:11 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:40:11 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:46 +0000 UTC }]
Nov 11 22:40:18.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:18.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:18.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:18.065: INFO:
Nov 11 22:40:20.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:20.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:20.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:20.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Nov 11 22:40:20.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:20.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:20.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:20.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:20.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:20.065: INFO:
Nov 11 22:40:22.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:22.067: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:22.067: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:22.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Nov 11 22:40:22.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:22.067: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:22.067: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:22.067: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:22.067: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:22.067: INFO:
Nov 11 22:40:24.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:24.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:24.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:24.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Nov 11 22:40:24.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:24.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:24.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:24.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:24.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:24.066: INFO:
Nov 11 22:40:26.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:26.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:26.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:26.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Nov 11 22:40:26.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:26.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:26.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:26.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:26.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:26.064: INFO:
Nov 11 22:40:28.075: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:28.075: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:28.075: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:28.075: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Nov 11 22:40:28.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:28.075: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:28.075: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:28.075: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:28.075: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:28.075: INFO:
Nov 11 22:40:30.068: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:30.068: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:30.068: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:30.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Nov 11 22:40:30.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:30.068: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:30.068: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:30.068: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:30.068: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:30.068: INFO:
Nov 11 22:40:32.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:32.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:32.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:32.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
Nov 11 22:40:32.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:32.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:32.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:32.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:32.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:32.063: INFO:
Nov 11 22:40:34.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:34.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:34.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:34.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
Nov 11 22:40:34.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:34.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:34.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:34.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:34.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:34.065: INFO:
Nov 11 22:40:36.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:36.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:36.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:36.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
Nov 11 22:40:36.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:36.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:36.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:36.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:36.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:36.064: INFO:
Nov 11 22:40:38.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:38.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:38.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:38.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
Nov 11 22:40:38.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:38.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:38.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:38.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:38.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:38.066: INFO:
Nov 11 22:40:40.072: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:40.072: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:40.072: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:40.072: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
Nov 11 22:40:40.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:40.072: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:40.072: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:40.072: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:40.072: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:40.072: INFO:
Nov 11 22:40:42.072: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:42.072: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:42.072: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:42.072: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
Nov 11 22:40:42.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:42.072: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:42.072: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:42.072: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:42.072: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:42.072: INFO:
Nov 11 22:40:44.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:44.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:44.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:44.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
Nov 11 22:40:44.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:44.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:44.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:44.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:44.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:44.063: INFO:
Nov 11 22:40:46.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:46.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:46.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:46.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
Nov 11 22:40:46.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:46.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:46.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:46.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:46.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:46.066: INFO:
Nov 11 22:40:48.067: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:48.067: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:48.067: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:48.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
Nov 11 22:40:48.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:48.067: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:48.067: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:48.067: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:48.067: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:48.067: INFO:
Nov 11 22:40:50.069: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:50.069: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:50.069: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:50.069: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
Nov 11 22:40:50.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:50.069: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:50.069: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:50.069: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:50.069: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:50.069: INFO:
Nov 11 22:40:52.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:52.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:52.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:52.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
Nov 11 22:40:52.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:52.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:52.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:52.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:52.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:52.066: INFO:
Nov 11 22:40:54.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:54.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:54.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:54.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
Nov 11 22:40:54.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:54.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:54.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:54.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:54.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:54.066: INFO:
Nov 11 22:40:56.069: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:56.069: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:56.069: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:56.069: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
Nov 11 22:40:56.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:56.069: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:56.069: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:56.069: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:56.069: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:56.069: INFO:
Nov 11 22:40:58.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:58.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:58.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:40:58.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
Nov 11 22:40:58.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:40:58.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:40:58.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:58.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:58.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:40:58.066: INFO:
Nov 11 22:41:00.075: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:00.075: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:00.075: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:00.075: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
Nov 11 22:41:00.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:00.075: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:00.075: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:00.075: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:00.075: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:00.075: INFO:
Nov 11 22:41:02.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:02.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:02.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:02.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
Nov 11 22:41:02.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:02.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:02.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:02.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:02.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:02.065: INFO:
Nov 11 22:41:04.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:04.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:04.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:04.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
Nov 11 22:41:04.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:04.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:04.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:04.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:04.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:04.061: INFO:
Nov 11 22:41:06.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:06.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:06.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:06.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
Nov 11 22:41:06.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:06.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:06.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:06.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:06.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:06.064: INFO:
Nov 11 22:41:08.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:08.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:08.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:08.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
Nov 11 22:41:08.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:08.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:08.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:08.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:08.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:08.066: INFO:
Nov 11 22:41:10.067: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:10.067: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:10.067: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:10.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
Nov 11 22:41:10.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:10.067: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:10.067: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:10.067: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:10.067: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:10.067: INFO:
Nov 11 22:41:12.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:12.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:12.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:12.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
Nov 11 22:41:12.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:12.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:12.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:12.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:12.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:12.065: INFO:
Nov 11 22:41:14.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:14.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:14.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:14.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
Nov 11 22:41:14.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:14.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:14.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:14.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:14.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:14.063: INFO:
Nov 11 22:41:16.068: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:16.068: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:16.068: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:16.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
Nov 11 22:41:16.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:16.068: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:16.068: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:16.068: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:16.068: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:16.068: INFO:
Nov 11 22:41:18.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:18.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:18.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:18.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
Nov 11 22:41:18.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:18.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:18.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:18.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:18.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:18.065: INFO:
Nov 11 22:41:20.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:20.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:20.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:20.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
Nov 11 22:41:20.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:20.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:20.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:20.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:20.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:20.065: INFO:
Nov 11 22:41:22.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:22.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:22.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:22.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
Nov 11 22:41:22.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:22.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:22.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:22.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:22.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:22.065: INFO:
Nov 11 22:41:24.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:24.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:24.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:24.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
Nov 11 22:41:24.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:24.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:24.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:24.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:24.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:24.066: INFO:
Nov 11 22:41:26.245: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:26.245: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:26.245: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:26.245: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
Nov 11 22:41:26.245: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:26.245: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:26.245: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:26.245: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:26.245: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:26.245: INFO:
Nov 11 22:41:28.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:28.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:28.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:28.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
Nov 11 22:41:28.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:28.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:28.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:28.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:28.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:28.066: INFO:
Nov 11 22:41:30.068: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:30.068: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:30.068: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:30.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
Nov 11 22:41:30.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:30.068: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:30.068: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:30.068: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:30.068: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:30.068: INFO:
Nov 11 22:41:32.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:32.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:32.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:32.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
Nov 11 22:41:32.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:32.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:32.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:32.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:32.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:32.063: INFO:
Nov 11 22:41:34.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:34.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:34.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:34.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
Nov 11 22:41:34.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:34.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:34.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:34.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:34.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:34.065: INFO:
Nov 11 22:41:36.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:36.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:36.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:36.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
Nov 11 22:41:36.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:36.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:36.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:36.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:36.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:36.064: INFO:
Nov 11 22:41:38.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:38.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:38.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:38.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
Nov 11 22:41:38.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:38.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:38.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:38.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:38.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:38.065: INFO:
Nov 11 22:41:40.071: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:40.071: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:40.071: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:40.071: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
Nov 11 22:41:40.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:40.071: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:40.071: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:40.071: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:40.071: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:40.071: INFO:
Nov 11 22:41:42.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:42.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:42.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:42.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
Nov 11 22:41:42.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:42.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:42.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:42.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:42.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:42.064: INFO:
Nov 11 22:41:44.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:44.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:44.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:44.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
Nov 11 22:41:44.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:44.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:44.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:44.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:44.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:44.064: INFO:
Nov 11 22:41:46.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:46.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:46.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:46.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
Nov 11 22:41:46.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:46.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:46.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:46.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:46.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:46.061: INFO:
Nov 11 22:41:48.070: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:48.070: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:48.070: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:48.070: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
Nov 11 22:41:48.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:48.070: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:48.070: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:48.070: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:48.070: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:48.070: INFO:
Nov 11 22:41:50.068: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:50.068: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:50.068: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:50.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
Nov 11 22:41:50.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:50.068: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:50.068: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:50.068: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:50.068: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:50.068: INFO:
Nov 11 22:41:52.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:52.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:52.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:52.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
Nov 11 22:41:52.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:52.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:52.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:52.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:52.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:52.062: INFO:
Nov 11 22:41:54.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:54.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:54.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:54.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
Nov 11 22:41:54.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:54.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:54.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:54.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:54.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:54.064: INFO:
Nov 11 22:41:56.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:56.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:56.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:56.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
Nov 11 22:41:56.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:56.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:56.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:56.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:56.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:56.065: INFO:
Nov 11 22:41:58.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:58.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:58.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:41:58.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
Nov 11 22:41:58.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:41:58.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:41:58.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:58.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:58.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:41:58.063: INFO:
Nov 11 22:42:00.068: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:00.068: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:00.068: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:00.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
Nov 11 22:42:00.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:00.068: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:00.068: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:00.068: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:00.068: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:00.068: INFO:
Nov 11 22:42:02.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:02.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:02.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:02.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
Nov 11 22:42:02.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:02.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:02.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:02.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:02.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:02.065: INFO:
Nov 11 22:42:04.069: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:04.069: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:04.069: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:04.069: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
Nov 11 22:42:04.069: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:04.069: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:04.069: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:04.069: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:04.069: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:04.069: INFO:
Nov 11 22:42:06.068: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:06.068: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:06.068: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:06.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
Nov 11 22:42:06.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:06.068: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:06.068: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:06.069: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:06.069: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:06.069: INFO:
Nov 11 22:42:08.067: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:08.067: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:08.067: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:08.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
Nov 11 22:42:08.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:08.067: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:08.067: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:08.067: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:08.067: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:08.067: INFO:
Nov 11 22:42:10.072: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:10.072: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:10.072: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:10.072: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
Nov 11 22:42:10.072: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:10.072: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:10.072: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:10.072: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:10.072: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:10.072: INFO:
Nov 11 22:42:12.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:12.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:12.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:12.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
Nov 11 22:42:12.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:12.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:12.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:12.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:12.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:12.064: INFO:
Nov 11 22:42:14.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:14.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:14.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:14.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
Nov 11 22:42:14.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:14.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:14.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:14.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:14.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:14.064: INFO:
Nov 11 22:42:16.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:16.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:16.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:16.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
Nov 11 22:42:16.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:16.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:16.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:16.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:16.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:16.063: INFO:
Nov 11 22:42:18.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:18.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:18.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:18.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
Nov 11 22:42:18.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:18.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:18.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:18.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:18.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:18.064: INFO:
Nov 11 22:42:20.241: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:20.241: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:20.241: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:20.241: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
Nov 11 22:42:20.241: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:20.241: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:20.241: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:20.241: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:20.241: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:20.241: INFO:
Nov 11 22:42:22.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:22.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:22.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:22.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
Nov 11 22:42:22.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:22.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:22.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:22.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:22.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:22.061: INFO:
Nov 11 22:42:24.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:24.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:24.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:24.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
Nov 11 22:42:24.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:24.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:24.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:24.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:24.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:24.062: INFO:
Nov 11 22:42:26.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:26.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:26.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:26.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
Nov 11 22:42:26.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:26.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:26.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:26.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:26.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:26.064: INFO:
Nov 11 22:42:28.075: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:28.075: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:28.075: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:28.075: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
Nov 11 22:42:28.075: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:28.075: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:28.075: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:28.075: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:28.075: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:28.075: INFO:
Nov 11 22:42:30.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:30.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:30.067: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:30.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
Nov 11 22:42:30.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:30.067: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:30.067: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:30.067: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:30.067: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:30.067: INFO:
Nov 11 22:42:32.068: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:32.068: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:32.068: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:32.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
Nov 11 22:42:32.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:32.068: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:32.068: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:32.068: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:32.068: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:32.068: INFO:
Nov 11 22:42:34.074: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:34.074: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:34.074: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:34.074: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
Nov 11 22:42:34.074: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:34.074: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:34.074: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:34.074: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:34.074: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:34.074: INFO:
Nov 11 22:42:36.068: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:36.068: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:36.068: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:36.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
Nov 11 22:42:36.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:36.068: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:36.068: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:36.068: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:36.068: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:36.068: INFO:
Nov 11 22:42:38.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:38.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:38.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:38.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
Nov 11 22:42:38.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:38.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:38.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:38.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:38.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:38.064: INFO:
Nov 11 22:42:40.068: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:40.068: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:40.068: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:40.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
Nov 11 22:42:40.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:40.068: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:40.068: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:40.068: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:40.068: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:40.068: INFO:
Nov 11 22:42:42.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:42.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:42.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:42.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
Nov 11 22:42:42.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:42.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:42.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:42.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:42.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:42.066: INFO:
Nov 11 22:42:44.068: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:44.068: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:44.068: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:44.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
Nov 11 22:42:44.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:44.068: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:44.068: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:44.068: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:44.068: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:44.068: INFO:
Nov 11 22:42:46.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:46.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:46.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:46.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
Nov 11 22:42:46.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:46.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:46.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:46.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:46.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:46.066: INFO:
Nov 11 22:42:48.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:48.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:48.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:48.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
Nov 11 22:42:48.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:48.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:48.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:48.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:48.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:48.063: INFO:
Nov 11 22:42:50.067: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:50.067: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:50.067: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:50.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
Nov 11 22:42:50.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:50.067: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:50.067: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:50.067: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:50.067: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:50.067: INFO:
Nov 11 22:42:52.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:52.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:52.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:52.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
Nov 11 22:42:52.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:52.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:52.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:52.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:52.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:52.064: INFO:
Nov 11 22:42:54.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:54.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:54.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:54.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
Nov 11 22:42:54.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:54.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:54.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:54.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:54.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:54.062: INFO:
Nov 11 22:42:56.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:56.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:56.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:56.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
Nov 11 22:42:56.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:56.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:56.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:56.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:56.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:56.065: INFO:
Nov 11 22:42:58.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:58.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:58.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:42:58.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
Nov 11 22:42:58.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:42:58.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:42:58.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:58.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:58.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:42:58.062: INFO:
Nov 11 22:43:00.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:00.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:00.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:00.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
Nov 11 22:43:00.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:00.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:00.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:00.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:00.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:00.065: INFO:
Nov 11 22:43:02.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:02.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:02.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:02.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
Nov 11 22:43:02.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:02.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:02.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:02.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:02.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:02.063: INFO:
Nov 11 22:43:04.068: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:04.068: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:04.068: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:04.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
Nov 11 22:43:04.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:04.068: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:04.068: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:04.068: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:04.068: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:04.068: INFO:
Nov 11 22:43:06.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:06.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:06.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:06.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
Nov 11 22:43:06.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:06.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:06.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:06.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:06.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:06.063: INFO:
Nov 11 22:43:08.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:08.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:08.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:08.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
Nov 11 22:43:08.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:08.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:08.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:08.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:08.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:08.066: INFO:
Nov 11 22:43:10.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:10.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:10.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:10.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
Nov 11 22:43:10.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:10.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:10.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:10.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:10.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:10.066: INFO:
Nov 11 22:43:12.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:12.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:12.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:12.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
Nov 11 22:43:12.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:12.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:12.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:12.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:12.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:12.062: INFO:
Nov 11 22:43:14.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:14.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:14.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:14.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
Nov 11 22:43:14.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:14.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:14.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:14.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:14.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:14.063: INFO:
Nov 11 22:43:16.067: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:16.067: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:16.067: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:16.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
Nov 11 22:43:16.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:16.067: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:16.067: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:16.067: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:16.067: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:16.067: INFO:
Nov 11 22:43:18.067: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:18.067: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:18.067: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:18.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
Nov 11 22:43:18.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:18.067: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:18.067: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:18.067: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:18.067: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:18.067: INFO:
Nov 11 22:43:20.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:20.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:20.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:20.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
Nov 11 22:43:20.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:20.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:20.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:20.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:20.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:20.066: INFO:
Nov 11 22:43:22.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:22.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:22.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:22.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
Nov 11 22:43:22.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:22.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:22.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:22.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:22.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:22.065: INFO:
Nov 11 22:43:24.067: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:24.067: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:24.067: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:24.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
Nov 11 22:43:24.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:24.067: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:24.067: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:24.067: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:24.067: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:24.067: INFO:
Nov 11 22:43:26.070: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:26.070: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:26.070: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:26.070: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
Nov 11 22:43:26.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:26.070: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:26.070: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:26.070: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:26.070: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:26.070: INFO:
Nov 11 22:43:28.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:28.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:28.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:28.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
Nov 11 22:43:28.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:28.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:28.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:28.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:28.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:28.065: INFO:
Nov 11 22:43:30.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:30.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:30.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:30.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
Nov 11 22:43:30.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:30.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:30.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:30.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:30.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:30.062: INFO:
Nov 11 22:43:32.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:32.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:32.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:32.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
Nov 11 22:43:32.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:32.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:32.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:32.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:32.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:32.062: INFO:
Nov 11 22:43:34.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:34.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:34.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:34.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
Nov 11 22:43:34.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:34.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:34.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:34.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:34.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:34.064: INFO:
Nov 11 22:43:36.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:36.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:36.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:36.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
Nov 11 22:43:36.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:36.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:36.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:36.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:36.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:36.065: INFO:
Nov 11 22:43:38.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:38.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:38.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:38.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
Nov 11 22:43:38.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:38.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:38.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:38.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:38.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:38.062: INFO:
Nov 11 22:43:40.067: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:40.067: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:40.067: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:40.067: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
Nov 11 22:43:40.067: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:40.067: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:40.067: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:40.067: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:40.067: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:40.067: INFO:
Nov 11 22:43:42.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:42.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:42.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:42.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
Nov 11 22:43:42.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:42.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:42.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:42.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:42.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:42.061: INFO:
Nov 11 22:43:44.070: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:44.070: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:44.070: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:44.070: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
Nov 11 22:43:44.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:44.070: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:44.070: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:44.070: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:44.070: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:44.070: INFO:
Nov 11 22:43:46.068: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:46.068: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:46.068: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:46.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
Nov 11 22:43:46.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:46.068: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:46.068: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:46.068: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:46.068: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:46.068: INFO:
Nov 11 22:43:48.070: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:48.070: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:48.070: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:48.070: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
Nov 11 22:43:48.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:48.070: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:48.070: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:48.070: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:48.070: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:48.070: INFO:
Nov 11 22:43:50.070: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:50.070: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:50.070: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:50.070: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
Nov 11 22:43:50.070: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:50.070: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:50.070: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:50.070: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:50.070: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:50.070: INFO:
Nov 11 22:43:52.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:52.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:52.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:52.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
Nov 11 22:43:52.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:52.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:52.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:52.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:52.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:52.062: INFO:
Nov 11 22:43:54.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:54.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:54.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:54.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
Nov 11 22:43:54.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:54.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:54.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:54.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:54.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:54.064: INFO:
Nov 11 22:43:56.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:56.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:56.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:56.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
Nov 11 22:43:56.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:56.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:56.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:56.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:56.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:56.059: INFO:
Nov 11 22:43:58.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:58.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:58.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:43:58.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
Nov 11 22:43:58.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:43:58.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:43:58.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:58.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:58.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:43:58.061: INFO:
Nov 11 22:44:00.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:00.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:00.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:00.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
Nov 11 22:44:00.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:00.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:00.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:00.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:00.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:00.059: INFO:
Nov 11 22:44:02.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:02.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:02.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:02.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
Nov 11 22:44:02.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:02.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:02.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:02.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:02.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:02.059: INFO:
Nov 11 22:44:04.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:04.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:04.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:04.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
Nov 11 22:44:04.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:04.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:04.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:04.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:04.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:04.059: INFO:
Nov 11 22:44:06.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:06.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:06.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:06.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
Nov 11 22:44:06.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:06.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:06.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:06.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:06.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:06.060: INFO:
Nov 11 22:44:08.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:08.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:08.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:08.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
Nov 11 22:44:08.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:08.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:08.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:08.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:08.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:08.063: INFO:
Nov 11 22:44:10.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:10.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:10.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:10.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
Nov 11 22:44:10.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:10.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:10.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:10.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:10.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:10.061: INFO:
Nov 11 22:44:12.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:12.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:12.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:12.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
Nov 11 22:44:12.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:12.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:12.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:12.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:12.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:12.060: INFO:
Nov 11 22:44:14.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:14.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:14.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:14.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
Nov 11 22:44:14.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:14.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:14.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:14.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:14.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:14.060: INFO:
Nov 11 22:44:16.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:16.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:16.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:16.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
Nov 11 22:44:16.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:16.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:16.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:16.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:16.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:16.060: INFO:
Nov 11 22:44:18.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:18.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:18.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:18.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
Nov 11 22:44:18.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:18.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:18.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:18.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:18.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:18.059: INFO:
Nov 11 22:44:20.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:20.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:20.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:20.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
Nov 11 22:44:20.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:20.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:20.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:20.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:20.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:20.059: INFO:
Nov 11 22:44:22.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:22.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:22.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:22.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
Nov 11 22:44:22.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:22.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:22.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:22.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:22.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:22.059: INFO:
Nov 11 22:44:24.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:24.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:24.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:24.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
Nov 11 22:44:24.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:24.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:24.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:24.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:24.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:24.060: INFO:
Nov 11 22:44:26.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:26.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:26.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:26.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
Nov 11 22:44:26.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:26.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:26.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:26.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:26.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:26.059: INFO:
Nov 11 22:44:28.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:28.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:28.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:28.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
Nov 11 22:44:28.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:28.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:28.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:28.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:28.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:28.059: INFO:
Nov 11 22:44:30.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:30.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:30.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:30.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
Nov 11 22:44:30.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:30.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:30.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:30.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:30.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:30.062: INFO:
Nov 11 22:44:32.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:32.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:32.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:32.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
Nov 11 22:44:32.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:32.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:32.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:32.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:32.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:32.059: INFO:
Nov 11 22:44:34.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:34.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:34.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:34.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
Nov 11 22:44:34.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:34.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:34.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:34.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:34.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:34.058: INFO:
Nov 11 22:44:36.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:36.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:36.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:36.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
Nov 11 22:44:36.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:36.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:36.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:36.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:36.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:36.060: INFO:
Nov 11 22:44:38.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:38.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:38.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:38.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
Nov 11 22:44:38.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:38.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:38.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:38.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:38.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:38.058: INFO:
Nov 11 22:44:40.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:40.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:40.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:40.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
Nov 11 22:44:40.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:40.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:40.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:40.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:40.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:40.059: INFO:
Nov 11 22:44:42.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:42.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:42.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:42.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
Nov 11 22:44:42.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:42.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:42.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:42.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:42.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:42.059: INFO:
Nov 11 22:44:44.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:44.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:44.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:44.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
Nov 11 22:44:44.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:44.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:44.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:44.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:44.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:44.059: INFO:
Nov 11 22:44:46.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:46.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:46.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:46.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
Nov 11 22:44:46.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:46.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:46.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:46.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:46.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:46.059: INFO:
Nov 11 22:44:48.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:48.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:48.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:48.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
Nov 11 22:44:48.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:48.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:48.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:48.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:48.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:48.062: INFO:
Nov 11 22:44:50.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:50.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:50.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:50.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
Nov 11 22:44:50.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:50.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:50.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:50.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:50.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:50.059: INFO:
Nov 11 22:44:52.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:52.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:52.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:52.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
Nov 11 22:44:52.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:52.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:52.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:52.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:52.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:52.059: INFO:
Nov 11 22:44:54.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:54.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:54.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:54.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
Nov 11 22:44:54.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:54.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:54.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:54.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:54.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:54.061: INFO:
Nov 11 22:44:56.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:56.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:56.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:56.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
Nov 11 22:44:56.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:56.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:56.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:56.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:56.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:56.062: INFO:
Nov 11 22:44:58.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:58.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:58.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:44:58.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
Nov 11 22:44:58.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:44:58.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:44:58.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:58.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:58.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:44:58.060: INFO:
Nov 11 22:45:00.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:00.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:00.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:00.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
Nov 11 22:45:00.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:00.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:00.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:00.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:00.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:00.059: INFO:
Nov 11 22:45:02.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:02.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:02.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:02.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
Nov 11 22:45:02.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:02.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:02.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:02.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:02.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:02.060: INFO:
Nov 11 22:45:04.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:04.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:04.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:04.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
Nov 11 22:45:04.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:04.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:04.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:04.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:04.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:04.059: INFO:
Nov 11 22:45:06.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:06.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:06.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:06.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
Nov 11 22:45:06.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:06.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:06.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:06.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:06.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:06.060: INFO:
Nov 11 22:45:08.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:08.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:08.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:08.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
Nov 11 22:45:08.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:08.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:08.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:08.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:08.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:08.059: INFO:
Nov 11 22:45:10.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:10.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:10.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:10.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
Nov 11 22:45:10.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:10.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:10.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:10.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:10.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:10.060: INFO:
Nov 11 22:45:12.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:12.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:12.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:12.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
Nov 11 22:45:12.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:12.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:12.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:12.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:12.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:12.058: INFO:
Nov 11 22:45:14.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:14.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:14.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:14.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
Nov 11 22:45:14.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:14.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:14.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:14.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:14.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:14.059: INFO:
Nov 11 22:45:16.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:16.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:16.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:16.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
Nov 11 22:45:16.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:16.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:16.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:16.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:16.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:16.060: INFO:
Nov 11 22:45:18.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:18.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:18.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:18.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
Nov 11 22:45:18.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:18.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:18.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:18.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:18.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:18.060: INFO:
Nov 11 22:45:20.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:20.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:20.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:20.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
Nov 11 22:45:20.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:20.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:20.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:20.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:20.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:20.059: INFO:
Nov 11 22:45:22.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:22.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:22.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:22.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
Nov 11 22:45:22.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:22.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:22.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:22.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:22.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:22.058: INFO:
Nov 11 22:45:24.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:24.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:24.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:24.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
Nov 11 22:45:24.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:24.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:24.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:24.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:24.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:24.060: INFO:
Nov 11 22:45:26.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:26.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:26.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:26.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
Nov 11 22:45:26.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:26.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:26.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:26.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:26.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:26.061: INFO:
Nov 11 22:45:28.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:28.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:28.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:28.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
Nov 11 22:45:28.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:28.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:28.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:28.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:28.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:28.062: INFO:
Nov 11 22:45:30.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:30.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:30.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:30.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
Nov 11 22:45:30.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:30.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:30.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:30.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:30.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:30.059: INFO:
Nov 11 22:45:32.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:32.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:32.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:32.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
Nov 11 22:45:32.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:32.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:32.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:32.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:32.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:32.060: INFO:
Nov 11 22:45:34.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:34.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:34.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:34.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
Nov 11 22:45:34.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:34.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:34.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:34.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:34.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:34.061: INFO:
Nov 11 22:45:36.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:36.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:36.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:36.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
Nov 11 22:45:36.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:36.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:36.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:36.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:36.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:36.060: INFO:
Nov 11 22:45:38.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:38.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:38.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:38.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
Nov 11 22:45:38.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:38.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:38.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:38.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:38.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:38.059: INFO:
Nov 11 22:45:40.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:40.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:40.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:40.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
Nov 11 22:45:40.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:40.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:40.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:40.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:40.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:40.059: INFO:
Nov 11 22:45:42.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:42.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:42.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:42.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
Nov 11 22:45:42.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:42.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:42.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:42.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:42.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:42.059: INFO:
Nov 11 22:45:44.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:44.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:44.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:44.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
Nov 11 22:45:44.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:44.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:44.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:44.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:44.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:44.059: INFO:
Nov 11 22:45:46.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:46.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:46.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:46.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
Nov 11 22:45:46.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:46.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:46.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:46.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:46.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:46.061: INFO:
Nov 11 22:45:48.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:48.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:48.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:48.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
Nov 11 22:45:48.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:48.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:48.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:48.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:48.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:48.058: INFO:
Nov 11 22:45:50.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:50.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:50.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:50.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
Nov 11 22:45:50.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:50.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:50.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:50.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:50.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:50.061: INFO:
Nov 11 22:45:52.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:52.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:52.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:52.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
Nov 11 22:45:52.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:52.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:52.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:52.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:52.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:52.059: INFO:
Nov 11 22:45:54.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:54.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:54.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:54.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
Nov 11 22:45:54.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:54.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:54.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:54.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:54.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:54.059: INFO:
Nov 11 22:45:56.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:56.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:56.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:56.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
Nov 11 22:45:56.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:56.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:56.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:56.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:56.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:56.059: INFO:
Nov 11 22:45:58.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:58.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:58.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:45:58.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
Nov 11 22:45:58.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:45:58.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:45:58.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:58.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:58.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:45:58.061: INFO:
Nov 11 22:46:00.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:00.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:00.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:00.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
Nov 11 22:46:00.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:00.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:00.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:00.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:00.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:00.059: INFO:
Nov 11 22:46:02.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:02.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:02.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:02.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
Nov 11 22:46:02.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:02.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:02.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:02.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:02.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:02.058: INFO:
Nov 11 22:46:04.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:04.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:04.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:04.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
Nov 11 22:46:04.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:04.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:04.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:04.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:04.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:04.059: INFO:
Nov 11 22:46:06.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:06.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:06.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:06.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
Nov 11 22:46:06.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:06.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:06.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:06.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:06.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:06.059: INFO:
Nov 11 22:46:08.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:08.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:08.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:08.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
Nov 11 22:46:08.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:08.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:08.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:08.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:08.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:08.060: INFO:
Nov 11 22:46:10.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:10.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:10.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:10.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
Nov 11 22:46:10.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:10.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:10.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:10.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:10.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:10.064: INFO:
Nov 11 22:46:12.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:12.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:12.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:12.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
Nov 11 22:46:12.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:12.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:12.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:12.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:12.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:12.060: INFO:
Nov 11 22:46:14.068: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:14.068: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:14.068: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:14.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
Nov 11 22:46:14.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:14.068: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:14.068: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:14.068: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:14.068: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:14.068: INFO:
Nov 11 22:46:16.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:16.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:16.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:16.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
Nov 11 22:46:16.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:16.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:16.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:16.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:16.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:16.059: INFO:
Nov 11 22:46:18.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:18.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:18.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:18.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
Nov 11 22:46:18.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:18.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:18.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:18.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:18.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:18.061: INFO:
Nov 11 22:46:20.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:20.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:20.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:20.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
Nov 11 22:46:20.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:20.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:20.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:20.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:20.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:20.059: INFO:
Nov 11 22:46:22.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:22.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:22.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:22.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
Nov 11 22:46:22.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:22.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:22.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:22.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:22.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:22.058: INFO:
Nov 11 22:46:24.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:24.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:24.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:24.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
Nov 11 22:46:24.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:24.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:24.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:24.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:24.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:24.060: INFO:
Nov 11 22:46:26.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:26.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:26.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:26.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
Nov 11 22:46:26.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:26.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:26.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:26.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:26.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:26.062: INFO:
Nov 11 22:46:28.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:28.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:28.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:28.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
Nov 11 22:46:28.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:28.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:28.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:28.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:28.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:28.061: INFO:
Nov 11 22:46:30.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:30.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:30.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:30.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
Nov 11 22:46:30.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:30.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:30.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:30.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:30.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:30.060: INFO:
Nov 11 22:46:32.071: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:32.071: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:32.071: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:32.071: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
Nov 11 22:46:32.071: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:32.071: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:32.071: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:32.071: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:32.071: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:32.071: INFO:
Nov 11 22:46:34.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:34.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:34.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:34.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
Nov 11 22:46:34.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:34.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:34.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:34.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:34.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:34.064: INFO:
Nov 11 22:46:36.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:36.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:36.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:36.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
Nov 11 22:46:36.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:36.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:36.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:36.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:36.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:36.063: INFO:
Nov 11 22:46:38.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:38.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:38.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:38.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
Nov 11 22:46:38.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:38.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:38.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:38.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:38.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:38.063: INFO:
Nov 11 22:46:40.068: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:40.068: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:40.068: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:40.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
Nov 11 22:46:40.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:40.068: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:40.068: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:40.068: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:40.068: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:40.068: INFO:
Nov 11 22:46:42.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:42.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:42.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:42.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
Nov 11 22:46:42.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:42.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:42.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:42.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:42.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:42.060: INFO:
Nov 11 22:46:44.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:44.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:44.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:44.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
Nov 11 22:46:44.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:44.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:44.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:44.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:44.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:44.058: INFO:
Nov 11 22:46:46.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:46.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:46.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:46.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
Nov 11 22:46:46.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:46.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:46.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:46.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:46.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:46.061: INFO:
Nov 11 22:46:48.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:48.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:48.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:48.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
Nov 11 22:46:48.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:48.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:48.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:48.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:48.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:48.062: INFO:
Nov 11 22:46:50.234: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:50.234: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:50.234: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:50.234: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
Nov 11 22:46:50.234: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:50.234: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:50.234: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:50.234: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:50.234: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:50.234: INFO:
Nov 11 22:46:52.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:52.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:52.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:52.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
Nov 11 22:46:52.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:52.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:52.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:52.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:52.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:52.060: INFO:
Nov 11 22:46:54.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:54.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:54.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:54.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
Nov 11 22:46:54.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:54.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:54.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:54.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:54.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:54.060: INFO:
Nov 11 22:46:56.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:56.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:56.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:56.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
Nov 11 22:46:56.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:56.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:56.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:56.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:56.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:56.059: INFO:
Nov 11 22:46:58.068: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:58.068: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:58.068: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:46:58.068: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
Nov 11 22:46:58.068: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:46:58.068: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:46:58.068: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:58.068: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:58.068: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:46:58.068: INFO:
Nov 11 22:47:00.064: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:00.064: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:00.064: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:00.064: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
Nov 11 22:47:00.064: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:00.064: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:00.064: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:00.064: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:00.064: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:00.064: INFO:
Nov 11 22:47:02.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:02.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:02.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:02.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
Nov 11 22:47:02.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:02.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:02.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:02.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:02.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:02.060: INFO:
Nov 11 22:47:04.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:04.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:04.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:04.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
Nov 11 22:47:04.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:04.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:04.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:04.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:04.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:04.059: INFO:
Nov 11 22:47:06.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:06.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:06.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:06.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
Nov 11 22:47:06.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:06.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:06.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:06.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:06.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:06.059: INFO:
Nov 11 22:47:08.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:08.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:08.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:08.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
Nov 11 22:47:08.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:08.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:08.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:08.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:08.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:08.060: INFO:
Nov 11 22:47:10.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:10.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:10.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:10.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
Nov 11 22:47:10.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:10.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:10.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:10.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:10.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:10.061: INFO:
Nov 11 22:47:12.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:12.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:12.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:12.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
Nov 11 22:47:12.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:12.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:12.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:12.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:12.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:12.059: INFO:
Nov 11 22:47:14.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:14.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:14.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:14.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
Nov 11 22:47:14.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:14.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:14.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:14.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:14.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:14.058: INFO:
Nov 11 22:47:16.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:16.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:16.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:16.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
Nov 11 22:47:16.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:16.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:16.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:16.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:16.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:16.060: INFO:
Nov 11 22:47:18.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:18.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:18.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:18.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
Nov 11 22:47:18.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:18.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:18.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:18.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:18.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:18.059: INFO:
Nov 11 22:47:20.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:20.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:20.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:20.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
Nov 11 22:47:20.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:20.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:20.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:20.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:20.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:20.060: INFO:
Nov 11 22:47:22.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:22.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:22.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:22.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
Nov 11 22:47:22.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:22.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:22.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:22.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:22.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:22.060: INFO:
Nov 11 22:47:24.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:24.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:24.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:24.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
Nov 11 22:47:24.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:24.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:24.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:24.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:24.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:24.058: INFO:
Nov 11 22:47:26.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:26.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:26.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:26.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
Nov 11 22:47:26.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:26.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:26.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:26.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:26.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:26.059: INFO:
Nov 11 22:47:28.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:28.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:28.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:28.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
Nov 11 22:47:28.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:28.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:28.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:28.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:28.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:28.066: INFO:
Nov 11 22:47:30.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:30.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:30.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:30.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
Nov 11 22:47:30.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:30.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:30.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:30.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:30.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:30.060: INFO:
Nov 11 22:47:32.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:32.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:32.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:32.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
Nov 11 22:47:32.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:32.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:32.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:32.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:32.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:32.060: INFO:
Nov 11 22:47:34.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:34.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:34.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:34.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
Nov 11 22:47:34.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:34.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:34.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:34.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:34.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:34.058: INFO:
Nov 11 22:47:36.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:36.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:36.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:36.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
Nov 11 22:47:36.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:36.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:36.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:36.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:36.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:36.059: INFO:
Nov 11 22:47:38.236: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:38.236: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:38.236: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:38.236: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
Nov 11 22:47:38.236: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:38.236: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:38.236: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:38.236: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:38.236: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:38.236: INFO:
Nov 11 22:47:40.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:40.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:40.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:40.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
Nov 11 22:47:40.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:40.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:40.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:40.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:40.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:40.060: INFO:
Nov 11 22:47:42.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:42.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:42.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:42.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
Nov 11 22:47:42.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:42.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:42.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:42.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:42.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:42.061: INFO:
Nov 11 22:47:44.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:44.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:44.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:44.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
Nov 11 22:47:44.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:44.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:44.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:44.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:44.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:44.061: INFO:
Nov 11 22:47:46.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:46.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:46.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:46.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
Nov 11 22:47:46.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:46.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:46.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:46.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:46.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:46.060: INFO:
Nov 11 22:47:48.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:48.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:48.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:48.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
Nov 11 22:47:48.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:48.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:48.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:48.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:48.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:48.059: INFO:
Nov 11 22:47:50.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:50.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:50.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:50.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
Nov 11 22:47:50.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:50.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:50.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:50.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:50.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:50.059: INFO:
Nov 11 22:47:52.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:52.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:52.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:52.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
Nov 11 22:47:52.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:52.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:52.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:52.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:52.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:52.059: INFO:
Nov 11 22:47:54.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:54.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:54.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:54.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
Nov 11 22:47:54.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:54.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:54.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:54.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:54.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:54.060: INFO:
Nov 11 22:47:56.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:56.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:56.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:56.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
Nov 11 22:47:56.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:56.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:56.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:56.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:56.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:56.065: INFO:
Nov 11 22:47:58.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:58.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:58.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:47:58.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
Nov 11 22:47:58.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:47:58.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:47:58.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:58.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:58.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:47:58.063: INFO:
Nov 11 22:48:00.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:00.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:00.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:00.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
Nov 11 22:48:00.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:00.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:00.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:00.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:00.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:00.058: INFO:
Nov 11 22:48:02.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:02.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:02.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:02.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
Nov 11 22:48:02.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:02.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:02.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:02.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:02.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:02.059: INFO:
Nov 11 22:48:04.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:04.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:04.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:04.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
Nov 11 22:48:04.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:04.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:04.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:04.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:04.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:04.059: INFO:
Nov 11 22:48:06.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:06.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:06.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:06.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
Nov 11 22:48:06.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:06.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:06.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:06.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:06.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:06.059: INFO:
Nov 11 22:48:08.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:08.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:08.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:08.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
Nov 11 22:48:08.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:08.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:08.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:08.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:08.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:08.060: INFO:
Nov 11 22:48:10.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:10.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:10.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:10.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
Nov 11 22:48:10.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:10.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:10.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:10.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:10.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:10.059: INFO:
Nov 11 22:48:12.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:12.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:12.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:12.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
Nov 11 22:48:12.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:12.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:12.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:12.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:12.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:12.058: INFO:
Nov 11 22:48:14.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:14.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:14.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:14.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
Nov 11 22:48:14.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:14.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:14.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:14.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:14.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:14.061: INFO:
Nov 11 22:48:16.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:16.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:16.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:16.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
Nov 11 22:48:16.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:16.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:16.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:16.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:16.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:16.060: INFO:
Nov 11 22:48:18.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:18.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:18.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:18.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
Nov 11 22:48:18.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:18.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:18.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:18.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:18.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:18.060: INFO:
Nov 11 22:48:20.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:20.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:20.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:20.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
Nov 11 22:48:20.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:20.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:20.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:20.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:20.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:20.062: INFO:
Nov 11 22:48:22.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:22.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:22.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:22.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
Nov 11 22:48:22.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:22.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:22.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:22.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:22.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:22.059: INFO:
Nov 11 22:48:24.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:24.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:24.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:24.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
Nov 11 22:48:24.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:24.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:24.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:24.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:24.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:24.065: INFO:
Nov 11 22:48:26.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:26.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:26.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:26.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
Nov 11 22:48:26.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:26.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:26.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:26.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:26.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:26.061: INFO:
Nov 11 22:48:28.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:28.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:28.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:28.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
Nov 11 22:48:28.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:28.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:28.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:28.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:28.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:28.060: INFO:
Nov 11 22:48:30.237: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:30.237: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:30.237: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:30.237: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
Nov 11 22:48:30.237: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:30.237: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:30.237: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:30.237: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:30.237: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:30.237: INFO:
Nov 11 22:48:32.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:32.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:32.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:32.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
Nov 11 22:48:32.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:32.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:32.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:32.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:32.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:32.060: INFO:
Nov 11 22:48:34.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:34.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:34.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:34.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
Nov 11 22:48:34.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:34.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:34.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:34.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:34.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:34.059: INFO:
Nov 11 22:48:36.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:36.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:36.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:36.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
Nov 11 22:48:36.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:36.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:36.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:36.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:36.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:36.059: INFO:
Nov 11 22:48:38.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:38.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:38.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:38.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
Nov 11 22:48:38.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:38.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:38.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:38.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:38.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:38.063: INFO:
Nov 11 22:48:40.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:40.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:40.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:40.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
Nov 11 22:48:40.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:40.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:40.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:40.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:40.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:40.059: INFO:
Nov 11 22:48:42.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:42.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:42.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:42.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
Nov 11 22:48:42.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:42.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:42.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:42.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:42.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:42.059: INFO:
Nov 11 22:48:44.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:44.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:44.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:44.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
Nov 11 22:48:44.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:44.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:44.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:44.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:44.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:44.059: INFO:
Nov 11 22:48:46.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:46.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:46.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:46.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
Nov 11 22:48:46.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:46.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:46.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:46.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:46.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:46.061: INFO:
Nov 11 22:48:48.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:48.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:48.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:48.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
Nov 11 22:48:48.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:48.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:48.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:48.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:48.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:48.063: INFO:
Nov 11 22:48:50.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:50.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:50.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:50.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
Nov 11 22:48:50.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:50.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:50.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:50.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:50.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:50.061: INFO:
Nov 11 22:48:52.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:52.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:52.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:52.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
Nov 11 22:48:52.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:52.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:52.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:52.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:52.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:52.060: INFO:
Nov 11 22:48:54.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:54.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:54.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:54.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
Nov 11 22:48:54.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:54.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:54.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:54.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:54.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:54.059: INFO:
Nov 11 22:48:56.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:56.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:56.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:56.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
Nov 11 22:48:56.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:56.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:56.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:56.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:56.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:56.058: INFO:
Nov 11 22:48:58.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:58.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:58.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:48:58.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
Nov 11 22:48:58.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:48:58.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:48:58.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:58.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:58.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:48:58.061: INFO:
Nov 11 22:49:00.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:00.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:00.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:00.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
Nov 11 22:49:00.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:00.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:00.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:00.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:00.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:00.060: INFO:
Nov 11 22:49:02.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:02.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:02.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:02.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
Nov 11 22:49:02.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:02.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:02.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:02.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:02.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:02.059: INFO:
Nov 11 22:49:04.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:04.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:04.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:04.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
Nov 11 22:49:04.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:04.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:04.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:04.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:04.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:04.060: INFO:
Nov 11 22:49:06.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:06.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:06.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:06.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
Nov 11 22:49:06.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:06.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:06.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:06.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:06.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:06.062: INFO:
Nov 11 22:49:08.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:08.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:08.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:08.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
Nov 11 22:49:08.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:08.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:08.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:08.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:08.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:08.060: INFO:
Nov 11 22:49:10.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:10.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:10.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:10.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
Nov 11 22:49:10.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:10.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:10.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:10.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:10.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:10.061: INFO:
Nov 11 22:49:12.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:12.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:12.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:12.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
Nov 11 22:49:12.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:12.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:12.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:12.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:12.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:12.060: INFO:
Nov 11 22:49:14.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:14.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:14.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:14.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
Nov 11 22:49:14.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:14.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:14.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:14.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:14.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:14.059: INFO:
Nov 11 22:49:16.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:16.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:16.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:16.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
Nov 11 22:49:16.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:16.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:16.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:16.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:16.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:16.059: INFO:
Nov 11 22:49:18.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:18.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:18.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:18.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
Nov 11 22:49:18.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:18.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:18.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:18.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:18.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:18.062: INFO:
Nov 11 22:49:20.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:20.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:20.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:20.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
Nov 11 22:49:20.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:20.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:20.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:20.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:20.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:20.060: INFO:
Nov 11 22:49:22.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:22.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:22.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:22.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
Nov 11 22:49:22.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:22.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:22.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:22.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:22.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:22.060: INFO:
Nov 11 22:49:24.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:24.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:24.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:24.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
Nov 11 22:49:24.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:24.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:24.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:24.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:24.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:24.063: INFO:
Nov 11 22:49:26.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:26.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:26.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:26.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
Nov 11 22:49:26.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:26.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:26.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:26.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:26.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:26.059: INFO:
Nov 11 22:49:28.066: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:28.066: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:28.066: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:28.066: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
Nov 11 22:49:28.066: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:28.066: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:28.066: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:28.066: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:28.066: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:28.066: INFO:
Nov 11 22:49:30.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:30.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:30.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:30.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
Nov 11 22:49:30.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:30.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:30.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:30.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:30.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:30.059: INFO:
Nov 11 22:49:32.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:32.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:32.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:32.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
Nov 11 22:49:32.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:32.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:32.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:32.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:32.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:32.059: INFO:
Nov 11 22:49:34.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:34.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:34.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:34.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
Nov 11 22:49:34.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:34.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:34.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:34.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:34.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:34.061: INFO:
Nov 11 22:49:36.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:36.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:36.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:36.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
Nov 11 22:49:36.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:36.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:36.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:36.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:36.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:36.060: INFO:
Nov 11 22:49:38.061: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:38.061: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:38.061: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:38.061: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
Nov 11 22:49:38.061: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:38.061: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:38.061: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:38.061: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:38.061: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:38.061: INFO:
Nov 11 22:49:40.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:40.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:40.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:40.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
Nov 11 22:49:40.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:40.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:40.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:40.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:40.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:40.058: INFO:
Nov 11 22:49:42.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:42.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:42.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:42.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
Nov 11 22:49:42.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:42.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:42.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:42.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:42.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:42.059: INFO:
Nov 11 22:49:44.065: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:44.065: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:44.065: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:44.065: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
Nov 11 22:49:44.065: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:44.065: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:44.065: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:44.065: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:44.065: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:44.065: INFO:
Nov 11 22:49:46.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:46.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:46.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:46.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
Nov 11 22:49:46.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:46.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:46.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:46.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:46.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:46.060: INFO:
Nov 11 22:49:48.062: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:48.062: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:48.062: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:48.062: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
Nov 11 22:49:48.062: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:48.062: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:48.062: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:48.062: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:48.062: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:48.062: INFO:
Nov 11 22:49:50.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:50.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:50.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:50.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
Nov 11 22:49:50.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:50.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:50.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:50.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:50.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:50.059: INFO:
Nov 11 22:49:52.233: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:52.234: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:52.234: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:52.234: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
Nov 11 22:49:52.234: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:52.234: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:52.234: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:52.234: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:52.234: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:52.234: INFO:
Nov 11 22:49:54.059: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:54.059: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:54.059: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:54.059: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
Nov 11 22:49:54.059: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:54.059: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:54.059: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:54.059: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:54.059: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:54.059: INFO:
Nov 11 22:49:56.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:56.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:56.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:56.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
Nov 11 22:49:56.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:56.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:56.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:56.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:56.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:56.058: INFO:
Nov 11 22:49:58.060: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:58.060: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:58.060: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:49:58.060: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Nov 11 22:49:58.060: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:49:58.060: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:49:58.060: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:58.060: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:58.060: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:49:58.060: INFO:
Nov 11 22:50:00.063: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:50:00.063: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:50:00.063: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:50:00.063: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Nov 11 22:50:00.063: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:50:00.063: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:50:00.063: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:50:00.063: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:50:00.063: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:50:00.063: INFO:
Nov 11 22:50:02.058: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:50:02.058: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:50:02.058: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:50:02.058: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 11 22:50:02.058: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:50:02.058: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:50:02.058: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:50:02.058: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:50:02.058: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:50:02.058: INFO:
Nov 11 22:50:02.442: INFO: The status of Pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:50:02.442: INFO: The status of Pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:50:02.442: INFO: The status of Pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 11 22:50:02.442: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (601 seconds elapsed)
Nov 11 22:50:02.442: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 11 22:50:02.442: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:50:02.442: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:50:02.442: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:50:02.442: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:50:02.442: INFO:
�[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m11/11/22 22:50:02.442�[0m
�[1mSTEP:�[0m Found 128 events. �[38;5;243m11/11/22 22:50:02.578�[0m
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:39 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-vnsd21-control-plane-f8ggg_3c4ebbd5-f6e4-45b8-87a9-4ebbdc34564b became leader
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:40 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-vnsd21-control-plane-f8ggg_54f0231c-4e45-4fe2-bd8a-2004297c32d6 became leader
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:45 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-64475449fc to 2
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:45 +0000 UTC - event for coredns-64475449fc: {replicaset-controller } SuccessfulCreate: Created pod: coredns-64475449fc-m689b
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:45 +0000 UTC - event for coredns-64475449fc: {replicaset-controller } SuccessfulCreate: Created pod: coredns-64475449fc-67x4m
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:45 +0000 UTC - event for coredns-64475449fc-67x4m: {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..
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:45 +0000 UTC - event for coredns-64475449fc-m689b: {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..
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:45 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-ckc9k
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:45 +0000 UTC - event for kube-proxy-ckc9k: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-ckc9k to capz-conf-vnsd21-control-plane-f8ggg
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:46 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulDelete: Deleted pod: kube-proxy-ckc9k
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:48 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-95psr
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:48 +0000 UTC - event for kube-proxy-95psr: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-95psr to capz-conf-vnsd21-control-plane-f8ggg
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:50 +0000 UTC - event for kube-proxy-95psr: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.40_bff02826bda608"
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:55 +0000 UTC - event for kube-proxy-95psr: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Created: Created container kube-proxy
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:55 +0000 UTC - event for kube-proxy-95psr: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.40_bff02826bda608" in 5.402074149s (5.402087949s including waiting)
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:55 +0000 UTC - event for kube-proxy-95psr: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Started: Started container kube-proxy
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:58 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-954b56d74 to 1
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:58 +0000 UTC - event for metrics-server-954b56d74: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-954b56d74-fq5hw
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:35:58 +0000 UTC - event for metrics-server-954b56d74-fq5hw: {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..
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:01 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-56c5ff4bf8 to 1
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:01 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-56c5ff4bf8-lf7m2
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:01 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-lf7m2: {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..
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:01 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-tk8m7
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:01 +0000 UTC - event for calico-node-tk8m7: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-tk8m7 to capz-conf-vnsd21-control-plane-f8ggg
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:02 +0000 UTC - event for calico-node-tk8m7: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:09 +0000 UTC - event for calico-node-tk8m7: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Started: Started container upgrade-ipam
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:09 +0000 UTC - event for calico-node-tk8m7: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 7.016214916s (7.016232516s including waiting)
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:09 +0000 UTC - event for calico-node-tk8m7: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Created: Created container upgrade-ipam
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:12 +0000 UTC - event for calico-node-tk8m7: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Created: Created container install-cni
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:12 +0000 UTC - event for calico-node-tk8m7: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:12 +0000 UTC - event for calico-node-tk8m7: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Started: Started container install-cni
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:15 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-lf7m2: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-56c5ff4bf8-lf7m2 to capz-conf-vnsd21-control-plane-f8ggg
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:15 +0000 UTC - event for calico-node-tk8m7: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:15 +0000 UTC - event for coredns-64475449fc-67x4m: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-64475449fc-67x4m to capz-conf-vnsd21-control-plane-f8ggg
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:15 +0000 UTC - event for coredns-64475449fc-67x4m: {kubelet capz-conf-vnsd21-control-plane-f8ggg} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "a0f6cce13b457746356c925279611c3002b0896380fe566773eca5d7a390dc42": 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/
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:15 +0000 UTC - event for coredns-64475449fc-m689b: {kubelet capz-conf-vnsd21-control-plane-f8ggg} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "5f9250c8cd5dda7ac46cd9c98add1cf4416eee60f48908edc0d38bc446c9570e": 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/
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:15 +0000 UTC - event for coredns-64475449fc-m689b: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-64475449fc-m689b to capz-conf-vnsd21-control-plane-f8ggg
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:15 +0000 UTC - event for metrics-server-954b56d74-fq5hw: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-954b56d74-fq5hw to capz-conf-vnsd21-control-plane-f8ggg
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:16 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-lf7m2: {kubelet capz-conf-vnsd21-control-plane-f8ggg} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "4c876dbe1f0e2613ace8f529eec85b879bc24939f84a1fa176aee32d64e8b2b2": 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/
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:16 +0000 UTC - event for metrics-server-954b56d74-fq5hw: {kubelet capz-conf-vnsd21-control-plane-f8ggg} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "d9e04fdd890b6ac4f1374e7443a288845d9920ae7972b8c9d64ecf9ba9f70cf0": 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/
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:23 +0000 UTC - event for calico-node-tk8m7: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 7.371564996s (7.371572296s including waiting)
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:23 +0000 UTC - event for calico-node-tk8m7: {kubelet capz-conf-vnsd21-control-plane-f8ggg} 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
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:23 +0000 UTC - event for calico-node-tk8m7: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Created: Created container calico-node
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:23 +0000 UTC - event for calico-node-tk8m7: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Started: Started container calico-node
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:26 +0000 UTC - event for coredns-64475449fc-67x4m: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:27 +0000 UTC - event for coredns-64475449fc-67x4m: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Created: Created container coredns
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:27 +0000 UTC - event for coredns-64475449fc-67x4m: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Started: Started container coredns
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:27 +0000 UTC - event for coredns-64475449fc-67x4m: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Unhealthy: Readiness probe failed: Get "http://192.168.188.129:8181/ready": dial tcp 192.168.188.129:8181: connect: connection refused
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:28 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-lf7m2: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0"
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:29 +0000 UTC - event for coredns-64475449fc-m689b: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:30 +0000 UTC - event for coredns-64475449fc-m689b: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Started: Started container coredns
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:30 +0000 UTC - event for coredns-64475449fc-m689b: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Unhealthy: Readiness probe failed: Get "http://192.168.188.131:8181/ready": dial tcp 192.168.188.131:8181: connect: connection refused
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:30 +0000 UTC - event for coredns-64475449fc-m689b: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Created: Created container coredns
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:32 +0000 UTC - event for metrics-server-954b56d74-fq5hw: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:34 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-lf7m2: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 5.94225406s (5.942400662s including waiting)
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:34 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-lf7m2: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Created: Created container calico-kube-controllers
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:35 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-lf7m2: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Started: Started container calico-kube-controllers
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:38 +0000 UTC - event for metrics-server-954b56d74-fq5hw: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Created: Created container metrics-server
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:38 +0000 UTC - event for metrics-server-954b56d74-fq5hw: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Started: Started container metrics-server
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:36:38 +0000 UTC - event for metrics-server-954b56d74-fq5hw: {kubelet capz-conf-vnsd21-control-plane-f8ggg} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 3.652589861s (6.270872894s including waiting)
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:29 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-b7mdr
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:29 +0000 UTC - event for calico-node-windows-b7mdr: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-b7mdr to capz-conf-tg7l2
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:29 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-btbsm
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:29 +0000 UTC - event for containerd-logger-btbsm: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-btbsm to capz-conf-tg7l2
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:29 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-44tgx
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:29 +0000 UTC - event for kube-proxy-windows-44tgx: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-44tgx to capz-conf-tg7l2
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:31 +0000 UTC - event for calico-node-windows-b7mdr: {kubelet capz-conf-tg7l2} FailedMount: MountVolume.SetUp failed for volume "calico-static-rules" : failed to sync configmap cache: timed out waiting for the condition
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:31 +0000 UTC - event for calico-node-windows-b7mdr: {kubelet capz-conf-tg7l2} FailedMount: MountVolume.SetUp failed for volume "kubeadm-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:46 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-h6hwl
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:46 +0000 UTC - event for calico-node-windows-h6hwl: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-h6hwl to capz-conf-r49vt
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:46 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-gxkqj
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:46 +0000 UTC - event for containerd-logger-gxkqj: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-gxkqj to capz-conf-r49vt
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:46 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-hvzpm
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:46 +0000 UTC - event for kube-proxy-windows-hvzpm: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-hvzpm to capz-conf-r49vt
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:48 +0000 UTC - event for calico-node-windows-h6hwl: {kubelet capz-conf-r49vt} FailedMount: MountVolume.SetUp failed for volume "kubeadm-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:48 +0000 UTC - event for containerd-logger-gxkqj: {kubelet capz-conf-r49vt} FailedMount: MountVolume.SetUp failed for volume "containerd-logger-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:49 +0000 UTC - event for calico-node-windows-b7mdr: {kubelet capz-conf-tg7l2} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:49 +0000 UTC - event for containerd-logger-btbsm: {kubelet capz-conf-tg7l2} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:49 +0000 UTC - event for kube-proxy-windows-44tgx: {kubelet capz-conf-tg7l2} Pulled: Container image "sigwindowstools/kube-proxy:v1.26.0-beta.0.25_4b1b42624e06a9-calico-hostprocess" already present on machine
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:49 +0000 UTC - event for kube-proxy-windows-44tgx: {kubelet capz-conf-tg7l2} Created: Created container kube-proxy
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:49 +0000 UTC - event for kube-proxy-windows-44tgx: {kubelet capz-conf-tg7l2} Started: Started container kube-proxy
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:38:55 +0000 UTC - event for containerd-logger-btbsm: {kubelet capz-conf-tg7l2} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 6.5385441s (6.5385441s including waiting)
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:02 +0000 UTC - event for calico-node-windows-b7mdr: {kubelet capz-conf-tg7l2} Created: Created container install-cni
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:02 +0000 UTC - event for calico-node-windows-b7mdr: {kubelet capz-conf-tg7l2} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 7.0510642s (13.5226077s including waiting)
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:03 +0000 UTC - event for calico-node-windows-b7mdr: {kubelet capz-conf-tg7l2} Started: Started container install-cni
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:04 +0000 UTC - event for containerd-logger-btbsm: {kubelet capz-conf-tg7l2} Created: Created container containerd-logger
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:05 +0000 UTC - event for containerd-logger-btbsm: {kubelet capz-conf-tg7l2} Started: Started container containerd-logger
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:05 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-hjmmw
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:05 +0000 UTC - event for csi-proxy-hjmmw: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-hjmmw to capz-conf-tg7l2
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:06 +0000 UTC - event for calico-node-windows-h6hwl: {kubelet capz-conf-r49vt} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:06 +0000 UTC - event for containerd-logger-gxkqj: {kubelet capz-conf-r49vt} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:06 +0000 UTC - event for csi-proxy-hjmmw: {kubelet capz-conf-tg7l2} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:06 +0000 UTC - event for kube-proxy-windows-hvzpm: {kubelet capz-conf-r49vt} Pulled: Container image "sigwindowstools/kube-proxy:v1.26.0-beta.0.25_4b1b42624e06a9-calico-hostprocess" already present on machine
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:06 +0000 UTC - event for kube-proxy-windows-hvzpm: {kubelet capz-conf-r49vt} Started: Started container kube-proxy
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:06 +0000 UTC - event for kube-proxy-windows-hvzpm: {kubelet capz-conf-r49vt} Created: Created container kube-proxy
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:08 +0000 UTC - event for calico-node-windows-b7mdr: {kubelet capz-conf-tg7l2} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:11 +0000 UTC - event for containerd-logger-gxkqj: {kubelet capz-conf-r49vt} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 5.1264076s (5.1264076s including waiting)
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:18 +0000 UTC - event for calico-node-windows-h6hwl: {kubelet capz-conf-r49vt} Created: Created container install-cni
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:18 +0000 UTC - event for calico-node-windows-h6hwl: {kubelet capz-conf-r49vt} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 7.3564734s (12.4816424s including waiting)
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:19 +0000 UTC - event for calico-node-windows-h6hwl: {kubelet capz-conf-r49vt} Started: Started container install-cni
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:19 +0000 UTC - event for containerd-logger-gxkqj: {kubelet capz-conf-r49vt} Started: Started container containerd-logger
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:19 +0000 UTC - event for containerd-logger-gxkqj: {kubelet capz-conf-r49vt} Created: Created container containerd-logger
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:20 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-t7hcb
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:20 +0000 UTC - event for csi-proxy-t7hcb: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-t7hcb to capz-conf-r49vt
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:21 +0000 UTC - event for csi-proxy-t7hcb: {kubelet capz-conf-r49vt} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:24 +0000 UTC - event for calico-node-windows-h6hwl: {kubelet capz-conf-r49vt} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:25 +0000 UTC - event for csi-proxy-hjmmw: {kubelet capz-conf-tg7l2} Started: Started container csi-proxy
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:25 +0000 UTC - event for csi-proxy-hjmmw: {kubelet capz-conf-tg7l2} Created: Created container csi-proxy
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:25 +0000 UTC - event for csi-proxy-hjmmw: {kubelet capz-conf-tg7l2} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 19.1098107s (19.1098107s including waiting)
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:30 +0000 UTC - event for calico-node-windows-b7mdr: {kubelet capz-conf-tg7l2} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 5.219358s (22.3501389s including waiting)
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:30 +0000 UTC - event for calico-node-windows-b7mdr: {kubelet capz-conf-tg7l2} Created: Created container calico-node-startup
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:30 +0000 UTC - event for calico-node-windows-b7mdr: {kubelet capz-conf-tg7l2} Started: Started container calico-node-startup
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:30 +0000 UTC - event for calico-node-windows-b7mdr: {kubelet capz-conf-tg7l2} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:31 +0000 UTC - event for calico-node-windows-b7mdr: {kubelet capz-conf-tg7l2} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 929.527ms (929.527ms including waiting)
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:37 +0000 UTC - event for calico-node-windows-b7mdr: {kubelet capz-conf-tg7l2} Created: Created container calico-node-felix
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:38 +0000 UTC - event for calico-node-windows-b7mdr: {kubelet capz-conf-tg7l2} Started: Started container calico-node-felix
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:38 +0000 UTC - event for csi-proxy-t7hcb: {kubelet capz-conf-r49vt} Started: Started container csi-proxy
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:38 +0000 UTC - event for csi-proxy-t7hcb: {kubelet capz-conf-r49vt} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 16.6899725s (16.6899725s including waiting)
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:38 +0000 UTC - event for csi-proxy-t7hcb: {kubelet capz-conf-r49vt} Created: Created container csi-proxy
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:42 +0000 UTC - event for calico-node-windows-h6hwl: {kubelet capz-conf-r49vt} Created: Created container calico-node-startup
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:42 +0000 UTC - event for calico-node-windows-h6hwl: {kubelet capz-conf-r49vt} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 4.7163606s (18.6639522s including waiting)
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:43 +0000 UTC - event for calico-node-windows-h6hwl: {kubelet capz-conf-r49vt} Started: Started container calico-node-startup
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:43 +0000 UTC - event for calico-node-windows-h6hwl: {kubelet capz-conf-r49vt} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:43 +0000 UTC - event for calico-node-windows-h6hwl: {kubelet capz-conf-r49vt} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 822.0568ms (822.0956ms including waiting)
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:49 +0000 UTC - event for calico-node-windows-h6hwl: {kubelet capz-conf-r49vt} Created: Created container calico-node-felix
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:50 +0000 UTC - event for calico-node-windows-h6hwl: {kubelet capz-conf-r49vt} Started: Started container calico-node-felix
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:39:59 +0000 UTC - event for calico-node-windows-b7mdr: {kubelet capz-conf-tg7l2} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 852.7216ms (852.7216ms including waiting)
Nov 11 22:50:02.579: INFO: At 2022-11-11 22:40:12 +0000 UTC - event for calico-node-windows-h6hwl: {kubelet capz-conf-r49vt} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 821.1404ms (821.1903ms including waiting)
Nov 11 22:50:02.733: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 11 22:50:02.733: INFO: calico-kube-controllers-56c5ff4bf8-lf7m2 capz-conf-vnsd21-control-plane-f8ggg Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:15 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:35 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:35 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:15 +0000 UTC }]
Nov 11 22:50:02.733: INFO: calico-node-tk8m7 capz-conf-vnsd21-control-plane-f8ggg Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:15 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:24 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:24 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:01 +0000 UTC }]
Nov 11 22:50:02.733: INFO: calico-node-windows-b7mdr capz-conf-tg7l2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:08 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:40:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:40:06 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:29 +0000 UTC }]
Nov 11 22:50:02.733: INFO: calico-node-windows-h6hwl capz-conf-r49vt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:24 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:40:19 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:40:19 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:46 +0000 UTC }]
Nov 11 22:50:02.733: INFO: containerd-logger-btbsm capz-conf-tg7l2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:30 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:06 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:29 +0000 UTC }]
Nov 11 22:50:02.733: INFO: containerd-logger-gxkqj capz-conf-r49vt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:47 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:20 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:20 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:46 +0000 UTC }]
Nov 11 22:50:02.733: INFO: coredns-64475449fc-67x4m capz-conf-vnsd21-control-plane-f8ggg Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:15 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:35 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:35 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:15 +0000 UTC }]
Nov 11 22:50:02.733: INFO: coredns-64475449fc-m689b capz-conf-vnsd21-control-plane-f8ggg Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:15 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:35 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:35 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:15 +0000 UTC }]
Nov 11 22:50:02.733: INFO: csi-proxy-hjmmw capz-conf-tg7l2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:05 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:26 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:26 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:05 +0000 UTC }]
Nov 11 22:50:02.733: INFO: csi-proxy-t7hcb capz-conf-r49vt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:20 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:39 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:39 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:20 +0000 UTC }]
Nov 11 22:50:02.733: INFO: etcd-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:35:46 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:35:52 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:35:52 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:35:46 +0000 UTC }]
Nov 11 22:50:02.733: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:50:02.733: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:50:02.733: INFO: kube-proxy-95psr capz-conf-vnsd21-control-plane-f8ggg Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:35:48 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:35:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:35:56 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:35:48 +0000 UTC }]
Nov 11 22:50:02.733: INFO: kube-proxy-windows-44tgx capz-conf-tg7l2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:30 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:57 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:57 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:29 +0000 UTC }]
Nov 11 22:50:02.733: INFO: kube-proxy-windows-hvzpm capz-conf-r49vt Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:47 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:39:06 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:38:46 +0000 UTC }]
Nov 11 22:50:02.733: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Nov 11 22:50:02.733: INFO: metrics-server-954b56d74-fq5hw capz-conf-vnsd21-control-plane-f8ggg Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:15 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:37:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:37:06 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 22:36:15 +0000 UTC }]
Nov 11 22:50:02.733: INFO:
Nov 11 22:50:03.820: INFO:
Logging node info for node capz-conf-r49vt
Nov 11 22:50:03.933: INFO: Node Info: &Node{ObjectMeta:{capz-conf-r49vt 3d2fd681-0476-4dcb-92fd-8cbb66344b5b 2058 0 2022-11-11 22:38:46 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D4s_v3 beta.kubernetes.io/os:windows failure-domain.beta.kubernetes.io/region:northeurope failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-r49vt kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:northeurope topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-vnsd21 cluster.x-k8s.io/cluster-namespace:capz-conf-vnsd21 cluster.x-k8s.io/machine:capz-conf-vnsd21-md-win-694766cc66-fnd8r cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-vnsd21-md-win-694766cc66 kubeadm.alpha.kubernetes.io/cri-socket:npipe:////./pipe/containerd-containerd node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.1.0.4/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.45.65 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:f2:57:10 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-11 22:38:46 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-11 22:38:46 +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:node.kubernetes.io/windows-build":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2022-11-11 22:39:20 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-11 22:39:57 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {Go-http-client Update v1 2022-11-11 22:40:08 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{},"f:projectcalico.org/VXLANTunnelMACAddr":{}}}} status} {kubelet.exe Update v1 2022-11-11 22:49:59 +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-vnsd21/providers/Microsoft.Compute/virtualMachines/capz-conf-r49vt,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{8 0} {<nil>} 8 DecimalSI},cpu: {{4 0} {<nil>} 4 DecimalSI},ephemeral-storage: {{136912564224 0} {<nil>} 133703676Ki BinarySI},memory: {{17179398144 0} {<nil>} 16776756Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{8 0} {<nil>} 8 DecimalSI},cpu: {{4 0} {<nil>} 4 DecimalSI},ephemeral-storage: {{123221307598 0} {<nil>} 123221307598 DecimalSI},memory: {{17074540544 0} {<nil>} 16674356Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-11 22:49:59 +0000 UTC,LastTransitionTime:2022-11-11 22:38:46 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-11 22:49:59 +0000 UTC,LastTransitionTime:2022-11-11 22:38:46 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-11 22:49:59 +0000 UTC,LastTransitionTime:2022-11-11 22:38:46 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-11 22:49:59 +0000 UTC,LastTransitionTime:2022-11-11 22:39:20 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-r49vt,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-r49vt,SystemUUID:CECA2B6B-A384-4D51-9E0C-BA99FCEBBA04,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.26.0-beta.0.40+bff02826bda608-dirty,KubeProxyVersion:v1.26.0-beta.0.40+bff02826bda608-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.26.0-beta.0.25_4b1b42624e06a9-calico-hostprocess],SizeBytes:116182072,},ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/csi-proxy@sha256:96b4144986319a747ba599892454be2737aae6005d96b8e13ed481321ac3afba ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2],SizeBytes:109639330,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:104158827,},ContainerImage{Names:[docker.io/sigwindowstools/calico-install@sha256:1dac2d6534d9017f8967cc6238d6b448bdc1c978b5e8fea91bf39dc59d29881f docker.io/sigwindowstools/calico-install:v3.23.0-hostprocess],SizeBytes:47258351,},ContainerImage{Names:[docker.io/sigwindowstools/calico-node@sha256:6ea7a987c109fdc059a36bf4abc5267c6f3de99d02ef6e84f0826da2aa435ea5 docker.io/sigwindowstools/calico-node:v3.23.0-hostprocess],SizeBytes:27005594,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Nov 11 22:50:03.933: INFO:
Logging kubelet events for node capz-conf-r49vt
Nov 11 22:50:04.037: INFO:
Logging pods the kubelet thinks is on node capz-conf-r49vt
Nov 11 22:50:04.189: INFO: calico-node-windows-h6hwl started at 2022-11-11 22:38:47 +0000 UTC (1+2 container statuses recorded)
Nov 11 22:50:04.189: INFO: Init container install-cni ready: true, restart count 0
Nov 11 22:50:04.189: INFO: Container calico-node-felix ready: true, restart count 1
Nov 11 22:50:04.189: INFO: Container calico-node-startup ready: true, restart count 0
Nov 11 22:50:04.189: INFO: containerd-logger-gxkqj started at 2022-11-11 22:38:47 +0000 UTC (0+1 container statuses recorded)
Nov 11 22:50:04.189: INFO: Container containerd-logger ready: true, restart count 0
Nov 11 22:50:04.189: INFO: kube-proxy-windows-hvzpm started at 2022-11-11 22:38:47 +0000 UTC (0+1 container statuses recorded)
Nov 11 22:50:04.189: INFO: Container kube-proxy ready: true, restart count 0
Nov 11 22:50:04.189: INFO: csi-proxy-t7hcb started at 2022-11-11 22:39:20 +0000 UTC (0+1 container statuses recorded)
Nov 11 22:50:04.189: INFO: Container csi-proxy ready: true, restart count 0
Nov 11 22:50:04.634: INFO:
Latency metrics for node capz-conf-r49vt
Nov 11 22:50:04.634: INFO:
Logging node info for node capz-conf-tg7l2
Nov 11 22:50:04.747: INFO: Node Info: &Node{ObjectMeta:{capz-conf-tg7l2 9702b0de-131a-4197-b550-cebccbf3f1ea 1624 0 2022-11-11 22:38:29 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D4s_v3 beta.kubernetes.io/os:windows failure-domain.beta.kubernetes.io/region:northeurope failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-tg7l2 kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:northeurope topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-vnsd21 cluster.x-k8s.io/cluster-namespace:capz-conf-vnsd21 cluster.x-k8s.io/machine:capz-conf-vnsd21-md-win-694766cc66-979hq cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-vnsd21-md-win-694766cc66 kubeadm.alpha.kubernetes.io/cri-socket:npipe:////./pipe/containerd-containerd node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.1.0.5/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.198.193 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:2a:90:c0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-11 22:38:29 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-11 22:38:29 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:node.kubernetes.io/windows-build":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2022-11-11 22:39:05 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2022-11-11 22:39:55 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{},"f:projectcalico.org/VXLANTunnelMACAddr":{}}}} status} {manager Update v1 2022-11-11 22:39:55 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kubelet.exe Update v1 2022-11-11 22:45:08 +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-vnsd21/providers/Microsoft.Compute/virtualMachines/capz-conf-tg7l2,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{8 0} {<nil>} 8 DecimalSI},cpu: {{4 0} {<nil>} 4 DecimalSI},ephemeral-storage: {{136912564224 0} {<nil>} 133703676Ki BinarySI},memory: {{17179398144 0} {<nil>} 16776756Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{8 0} {<nil>} 8 DecimalSI},cpu: {{4 0} {<nil>} 4 DecimalSI},ephemeral-storage: {{123221307598 0} {<nil>} 123221307598 DecimalSI},memory: {{17074540544 0} {<nil>} 16674356Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-11 22:45:08 +0000 UTC,LastTransitionTime:2022-11-11 22:38:29 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-11 22:45:08 +0000 UTC,LastTransitionTime:2022-11-11 22:38:29 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-11 22:45:08 +0000 UTC,LastTransitionTime:2022-11-11 22:38:29 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-11 22:45:08 +0000 UTC,LastTransitionTime:2022-11-11 22:39:05 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-tg7l2,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-tg7l2,SystemUUID:221287C5-DC20-46E5-AE38-B1BA5883D2CB,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.26.0-beta.0.40+bff02826bda608-dirty,KubeProxyVersion:v1.26.0-beta.0.40+bff02826bda608-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.26.0-beta.0.25_4b1b42624e06a9-calico-hostprocess],SizeBytes:116182072,},ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/csi-proxy@sha256:96b4144986319a747ba599892454be2737aae6005d96b8e13ed481321ac3afba ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2],SizeBytes:109639330,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:104158827,},ContainerImage{Names:[docker.io/sigwindowstools/calico-install@sha256:1dac2d6534d9017f8967cc6238d6b448bdc1c978b5e8fea91bf39dc59d29881f docker.io/sigwindowstools/calico-install:v3.23.0-hostprocess],SizeBytes:47258351,},ContainerImage{Names:[docker.io/sigwindowstools/calico-node@sha256:6ea7a987c109fdc059a36bf4abc5267c6f3de99d02ef6e84f0826da2aa435ea5 docker.io/sigwindowstools/calico-node:v3.23.0-hostprocess],SizeBytes:27005594,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Nov 11 22:50:04.747: INFO:
Logging kubelet events for node capz-conf-tg7l2
Nov 11 22:50:04.850: INFO:
Logging pods the kubelet thinks is on node capz-conf-tg7l2
Nov 11 22:50:04.999: INFO: calico-node-windows-b7mdr started at 2022-11-11 22:38:30 +0000 UTC (1+2 container statuses recorded)
Nov 11 22:50:04.999: INFO: Init container install-cni ready: true, restart count 0
Nov 11 22:50:04.999: INFO: Container calico-node-felix ready: true, restart count 1
Nov 11 22:50:04.999: INFO: Container calico-node-startup ready: true, restart count 0
Nov 11 22:50:04.999: INFO: csi-proxy-hjmmw started at 2022-11-11 22:39:05 +0000 UTC (0+1 container statuses recorded)
Nov 11 22:50:04.999: INFO: Container csi-proxy ready: true, restart count 0
Nov 11 22:50:04.999: INFO: containerd-logger-btbsm started at 2022-11-11 22:38:30 +0000 UTC (0+1 container statuses recorded)
Nov 11 22:50:04.999: INFO: Container containerd-logger ready: true, restart count 0
Nov 11 22:50:04.999: INFO: kube-proxy-windows-44tgx started at 2022-11-11 22:38:30 +0000 UTC (0+1 container statuses recorded)
Nov 11 22:50:04.999: INFO: Container kube-proxy ready: true, restart count 1
Nov 11 22:50:05.454: INFO:
Latency metrics for node capz-conf-tg7l2
Nov 11 22:50:05.454: INFO:
Logging node info for node capz-conf-vnsd21-control-plane-f8ggg
Nov 11 22:50:05.571: INFO: Node Info: &Node{ObjectMeta:{capz-conf-vnsd21-control-plane-f8ggg 8d92949b-5d11-4e37-9352-ebc476ef9b1b 1787 0 2022-11-11 22:35:43 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:northeurope failure-domain.beta.kubernetes.io/zone:northeurope-3 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-vnsd21-control-plane-f8ggg 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-3] map[cluster.x-k8s.io/cluster-name:capz-conf-vnsd21 cluster.x-k8s.io/cluster-namespace:capz-conf-vnsd21 cluster.x-k8s.io/machine:capz-conf-vnsd21-control-plane-gc8c5 cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-vnsd21-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.188.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2022-11-11 22:35:43 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kubeadm Update v1 2022-11-11 22:35:44 +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 2022-11-11 22:35:56 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kube-controller-manager Update v1 2022-11-11 22:36:15 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2022-11-11 22:36:23 +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 2022-11-11 22:46:58 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-vnsd21/providers/Microsoft.Compute/virtualMachines/capz-conf-vnsd21-control-plane-f8ggg,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: {{8344719360 0} {<nil>} 8149140Ki 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: {{8239861760 0} {<nil>} 8046740Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2022-11-11 22:36:23 +0000 UTC,LastTransitionTime:2022-11-11 22:36:23 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-11 22:46:58 +0000 UTC,LastTransitionTime:2022-11-11 22:35:23 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-11 22:46:58 +0000 UTC,LastTransitionTime:2022-11-11 22:35:23 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-11 22:46:58 +0000 UTC,LastTransitionTime:2022-11-11 22:35:23 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-11 22:46:58 +0000 UTC,LastTransitionTime:2022-11-11 22:36:15 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-vnsd21-control-plane-f8ggg,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:afb97e3c350543928a947f7a110644ff,SystemUUID:c51a7cd7-c91a-984a-8d5a-2a20e2244743,BootID:307906f2-8ccc-4f3b-b8d4-ee48966e4bcd,KernelVersion:5.4.0-1091-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.26.0-beta.0.40+bff02826bda608,KubeProxyVersion:v1.26.0-beta.0.40+bff02826bda608,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:b83c1d70989e1fe87583607bf5aee1ee34e52773d4755b95f5cf5a451962f3a4 registry.k8s.io/etcd:3.5.5-0],SizeBytes:102417044,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:6f72b851544986cb0921b53ea655ec04c36131248f16d4ad110cb3ca0c369dc1 registry.k8s.io/etcd:3.5.4-0],SizeBytes:102157811,},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:a281d79c27f97065cc0ff8a6661080e75354cd8be47b399cd7807a5d5f1f9188 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.26.0-beta.0.25_4b1b42624e06a9],SizeBytes:35104230,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:4188262a351f156e8027ff81693d771c35b34b668cbd61e59c4a4490dd5c08f3 registry.k8s.io/kube-apiserver:v1.25.3],SizeBytes:34238163,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-controller-manager@sha256:94c2dc91a980cf5aca2c16af86d63344e81f66c54fdc256e264b683d1444dd9a gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.26.0-beta.0.25_4b1b42624e06a9],SizeBytes:32078767,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:d3a06262256f3e7578d5f77df137a8cdf58f9f498f35b5b56d116e8a7e31dc91 registry.k8s.io/kube-controller-manager:v1.25.3],SizeBytes:31261869,},ContainerImage{Names:[k8s.gcr.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 k8s.gcr.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:27c006f438e13a474f5167b413f017e63c61715b9f70b6cbd30faba1eaf9963c gcr.io/k8s-staging-ci-images/kube-proxy:v1.26.0-beta.0.25_4b1b42624e06a9],SizeBytes:21418931,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:d945ad83444c0e92bc30dae7b4e56a1fa7805012b46a0c23410fe2aaca8b5b74 capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.40_bff02826bda608],SizeBytes:21417507,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:6bf25f038543e1f433cb7f2bdda445ed348c7b9279935ebc2ae4f432308ed82f registry.k8s.io/kube-proxy:v1.25.3],SizeBytes:20265805,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-scheduler@sha256:8150391a8ecb7ee775baddd27e7bb523220f2ef7f55824c82ca35a788391c670 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.26.0-beta.0.25_4b1b42624e06a9],SizeBytes:17334262,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:f478aa916568b00269068ff1e9ff742ecc16192eb6e371e30f69f75df904162e registry.k8s.io/kube-scheduler:v1.25.3],SizeBytes:15798744,},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:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Nov 11 22:50:05.571: INFO:
Logging kubelet events for node capz-conf-vnsd21-control-plane-f8ggg
Nov 11 22:50:05.674: INFO:
Logging pods the kubelet thinks is on node capz-conf-vnsd21-control-plane-f8ggg
Nov 11 22:50:05.881: INFO: calico-kube-controllers-56c5ff4bf8-lf7m2 started at 2022-11-11 22:36:15 +0000 UTC (0+1 container statuses recorded)
Nov 11 22:50:05.881: INFO: Container calico-kube-controllers ready: true, restart count 0
Nov 11 22:50:05.881: INFO: kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg started at <nil> (0+0 container statuses recorded)
Nov 11 22:50:05.881: INFO: kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg started at <nil> (0+0 container statuses recorded)
Nov 11 22:50:05.881: INFO: kube-proxy-95psr started at 2022-11-11 22:35:48 +0000 UTC (0+1 container statuses recorded)
Nov 11 22:50:05.881: INFO: Container kube-proxy ready: true, restart count 0
Nov 11 22:50:05.881: INFO: calico-node-tk8m7 started at 2022-11-11 22:36:01 +0000 UTC (2+1 container statuses recorded)
Nov 11 22:50:05.881: INFO: Init container upgrade-ipam ready: true, restart count 0
Nov 11 22:50:05.881: INFO: Init container install-cni ready: true, restart count 0
Nov 11 22:50:05.881: INFO: Container calico-node ready: true, restart count 0
Nov 11 22:50:05.881: INFO: coredns-64475449fc-67x4m started at 2022-11-11 22:36:15 +0000 UTC (0+1 container statuses recorded)
Nov 11 22:50:05.881: INFO: Container coredns ready: true, restart count 0
Nov 11 22:50:05.881: INFO: coredns-64475449fc-m689b started at 2022-11-11 22:36:15 +0000 UTC (0+1 container statuses recorded)
Nov 11 22:50:05.881: INFO: Container coredns ready: true, restart count 0
Nov 11 22:50:05.881: INFO: etcd-capz-conf-vnsd21-control-plane-f8ggg started at 2022-11-11 22:35:46 +0000 UTC (0+1 container statuses recorded)
Nov 11 22:50:05.881: INFO: Container etcd ready: true, restart count 0
Nov 11 22:50:05.881: INFO: kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg started at <nil> (0+0 container statuses recorded)
Nov 11 22:50:05.881: INFO: metrics-server-954b56d74-fq5hw started at 2022-11-11 22:36:15 +0000 UTC (0+1 container statuses recorded)
Nov 11 22:50:05.881: INFO: Container metrics-server ready: true, restart count 0
Nov 11 22:50:06.265: INFO:
Latency metrics for node capz-conf-vnsd21-control-plane-f8ggg
Nov 11 22:50:06.432: INFO: Running kubectl logs on non-ready containers in kube-system
Nov 11 22:50:06.816: INFO: Failed to get logs of pod kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg)
Nov 11 22:50:06.816: INFO: Logs of kube-system/kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg:kube-apiserver on node capz-conf-vnsd21-control-plane-f8ggg
Nov 11 22:50:06.816: INFO: : STARTLOG
ENDLOG for container kube-system:kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg:kube-apiserver
Nov 11 22:50:07.209: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg)
Nov 11 22:50:07.209: INFO: Logs of kube-system/kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg:kube-controller-manager on node capz-conf-vnsd21-control-plane-f8ggg
Nov 11 22:50:07.209: INFO: : STARTLOG
ENDLOG for container kube-system:kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg:kube-controller-manager
Nov 11 22:50:07.610: INFO: Failed to get logs of pod kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg)
Nov 11 22:50:07.610: INFO: Logs of kube-system/kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg:kube-scheduler on node capz-conf-vnsd21-control-plane-f8ggg
Nov 11 22:50:07.610: INFO: : STARTLOG
ENDLOG for container kube-system:kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg:kube-scheduler
Nov 11 22:50:07.610: FAIL: Error waiting for all pods to be running and ready: 3 / 18 pods in namespace kube-system are NOT in RUNNING and READY state in 10m0s
POD NODE PHASE GRACE CONDITIONS
kube-apiserver-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
kube-controller-manager-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
kube-scheduler-capz-conf-vnsd21-control-plane-f8ggg capz-conf-vnsd21-control-plane-f8ggg Pending []
Full Stack Trace
k8s.io/kubernetes/test/e2e.setupSuite()
test/e2e/e2e.go:249 +0x4de
k8s.io/kubernetes/test/e2e.glob..func1()
test/e2e/e2e.go:81 +0x8f
reflect.Value.call({0x66064e0?, 0x77d68f0?, 0x0?}, {0x74fe488, 0x4}, {0xc000bddf20, 0x0, 0x0?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x66064e0?, 0x77d68f0?, 0x0?}, {0xc000bddf20?, 0x0?, 0x0?})
/usr/local/go/src/reflect/value.go:368 +0xbc
from junit.kubetest.01.xml
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\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e suite report
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
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