PR #113742 pull-kubernetes-e2e-capz-windows-containerd #1593469275413155840
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | princepereira: Add a flag to HNS Load Balancer policy to hint HNS about the VIP being an External IP |
| Result | SUCCESS |
| Tests | 4 failed / 6 succeeded |
| Started | |
| Elapsed | 1h5m |
| Revision | e34de01e2c826cf3ace45e347e9b1c77b25972f1 |
| Refs |
113742 |
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({0x66a9bc0?, 0x78952d0?, 0x13?}, {0x75b6e72, 0x4}, {0xc000a3bf20, 0x0, 0x0?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x66a9bc0?, 0x78952d0?, 0x26cd5ed?}, {0xc0000a1f20?, 0x265bb67?, 0xc0000a1f20?})
/usr/local/go/src/reflect/value.go:368 +0xbc
[SynchronizedBeforeSuite] TOP-LEVEL
test/e2e/e2e.go:77
Nov 18 05:46:20.177: INFO: >>> kubeConfig: /tmp/kubeconfig
Nov 18 05:46:20.179: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Nov 18 05:46:20.368: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Nov 18 05:46:20.499: INFO: The status of Pod calico-node-windows-8ccjs is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:20.499: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:20.499: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:20.499: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:20.499: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Nov 18 05:46:20.499: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:20.499: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:20.499: INFO: calico-node-windows-8ccjs capz-conf-hh57q Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:25 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:46:14 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:46:14 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:44:49 +0000 UTC }]
Nov 18 05:46:20.499: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:20.499: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:20.499: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:20.499: INFO:
Nov 18 05:46:22.624: INFO: The status of Pod calico-node-windows-drqc6 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:22.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:22.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:22.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:22.624: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Nov 18 05:46:22.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:22.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:22.624: INFO: calico-node-windows-drqc6 capz-conf-lsdpj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:27 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:46:20 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:46:20 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:44:58 +0000 UTC }]
Nov 18 05:46:22.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:22.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:22.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:22.624: INFO:
Nov 18 05:46:24.629: INFO: The status of Pod calico-node-windows-drqc6 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:24.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:24.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:24.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:24.629: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Nov 18 05:46:24.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:24.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:24.629: INFO: calico-node-windows-drqc6 capz-conf-lsdpj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:27 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:46:20 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:46:20 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:44:58 +0000 UTC }]
Nov 18 05:46:24.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:24.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:24.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:24.629: INFO:
Nov 18 05:46:26.628: INFO: The status of Pod calico-node-windows-drqc6 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:26.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:26.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:26.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:26.628: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Nov 18 05:46:26.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:26.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:26.628: INFO: calico-node-windows-drqc6 capz-conf-lsdpj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:27 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:46:20 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:46:20 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:44:58 +0000 UTC }]
Nov 18 05:46:26.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:26.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:26.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:26.628: INFO:
Nov 18 05:46:28.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:28.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:28.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:28.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Nov 18 05:46:28.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:28.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:28.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:28.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:28.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:28.629: INFO:
Nov 18 05:46:30.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:30.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:30.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:30.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Nov 18 05:46:30.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:30.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:30.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:30.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:30.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:30.625: INFO:
Nov 18 05:46:32.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:32.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:32.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:32.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Nov 18 05:46:32.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:32.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:32.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:32.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:32.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:32.625: INFO:
Nov 18 05:46:34.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:34.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:34.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:34.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Nov 18 05:46:34.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:34.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:34.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:34.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:34.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:34.625: INFO:
Nov 18 05:46:36.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:36.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:36.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:36.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Nov 18 05:46:36.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:36.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:36.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:36.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:36.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:36.624: INFO:
Nov 18 05:46:38.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:38.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:38.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:38.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Nov 18 05:46:38.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:38.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:38.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:38.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:38.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:38.626: INFO:
Nov 18 05:46:40.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:40.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:40.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:40.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Nov 18 05:46:40.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:40.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:40.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:40.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:40.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:40.626: INFO:
Nov 18 05:46:42.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:42.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:42.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:42.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Nov 18 05:46:42.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:42.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:42.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:42.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:42.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:42.630: INFO:
Nov 18 05:46:44.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:44.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:44.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:44.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Nov 18 05:46:44.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:44.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:44.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:44.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:44.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:44.624: INFO:
Nov 18 05:46:46.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:46.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:46.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:46.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Nov 18 05:46:46.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:46.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:46.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:46.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:46.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:46.628: INFO:
Nov 18 05:46:48.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:48.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:48.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:48.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Nov 18 05:46:48.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:48.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:48.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:48.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:48.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:48.631: INFO:
Nov 18 05:46:50.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:50.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:50.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:50.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
Nov 18 05:46:50.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:50.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:50.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:50.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:50.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:50.627: INFO:
Nov 18 05:46:52.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:52.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:52.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:52.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
Nov 18 05:46:52.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:52.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:52.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:52.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:52.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:52.628: INFO:
Nov 18 05:46:54.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:54.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:54.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:54.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
Nov 18 05:46:54.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:54.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:54.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:54.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:54.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:54.625: INFO:
Nov 18 05:46:56.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:56.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:56.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:56.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
Nov 18 05:46:56.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:56.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:56.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:56.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:56.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:56.626: INFO:
Nov 18 05:46:58.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:58.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:58.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:46:58.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
Nov 18 05:46:58.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:46:58.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:46:58.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:58.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:58.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:46:58.626: INFO:
Nov 18 05:47:00.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:00.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:00.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:00.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
Nov 18 05:47:00.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:00.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:00.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:00.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:00.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:00.629: INFO:
Nov 18 05:47:02.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:02.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:02.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:02.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
Nov 18 05:47:02.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:02.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:02.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:02.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:02.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:02.629: INFO:
Nov 18 05:47:04.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:04.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:04.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:04.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
Nov 18 05:47:04.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:04.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:04.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:04.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:04.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:04.626: INFO:
Nov 18 05:47:06.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:06.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:06.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:06.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
Nov 18 05:47:06.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:06.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:06.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:06.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:06.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:06.628: INFO:
Nov 18 05:47:08.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:08.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:08.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:08.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
Nov 18 05:47:08.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:08.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:08.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:08.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:08.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:08.627: INFO:
Nov 18 05:47:10.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:10.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:10.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:10.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
Nov 18 05:47:10.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:10.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:10.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:10.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:10.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:10.625: INFO:
Nov 18 05:47:12.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:12.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:12.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:12.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
Nov 18 05:47:12.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:12.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:12.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:12.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:12.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:12.625: INFO:
Nov 18 05:47:14.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:14.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:14.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:14.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
Nov 18 05:47:14.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:14.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:14.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:14.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:14.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:14.625: INFO:
Nov 18 05:47:16.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:16.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:16.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:16.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
Nov 18 05:47:16.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:16.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:16.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:16.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:16.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:16.627: INFO:
Nov 18 05:47:18.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:18.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:18.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:18.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
Nov 18 05:47:18.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:18.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:18.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:18.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:18.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:18.625: INFO:
Nov 18 05:47:20.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:20.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:20.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:20.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
Nov 18 05:47:20.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:20.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:20.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:20.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:20.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:20.631: INFO:
Nov 18 05:47:22.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:22.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:22.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:22.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
Nov 18 05:47:22.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:22.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:22.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:22.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:22.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:22.625: INFO:
Nov 18 05:47:24.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:24.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:24.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:24.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
Nov 18 05:47:24.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:24.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:24.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:24.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:24.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:24.626: INFO:
Nov 18 05:47:26.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:26.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:26.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:26.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
Nov 18 05:47:26.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:26.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:26.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:26.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:26.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:26.625: INFO:
Nov 18 05:47:28.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:28.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:28.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:28.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
Nov 18 05:47:28.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:28.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:28.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:28.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:28.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:28.625: INFO:
Nov 18 05:47:30.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:30.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:30.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:30.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
Nov 18 05:47:30.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:30.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:30.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:30.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:30.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:30.629: INFO:
Nov 18 05:47:32.623: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:32.623: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:32.623: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:32.623: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
Nov 18 05:47:32.623: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:32.623: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:32.623: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:32.623: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:32.623: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:32.623: INFO:
Nov 18 05:47:34.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:34.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:34.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:34.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
Nov 18 05:47:34.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:34.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:34.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:34.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:34.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:34.628: INFO:
Nov 18 05:47:36.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:36.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:36.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:36.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
Nov 18 05:47:36.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:36.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:36.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:36.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:36.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:36.626: INFO:
Nov 18 05:47:38.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:38.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:38.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:38.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
Nov 18 05:47:38.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:38.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:38.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:38.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:38.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:38.625: INFO:
Nov 18 05:47:40.652: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:40.652: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:40.652: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:40.652: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
Nov 18 05:47:40.652: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:40.652: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:40.652: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:40.652: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:40.652: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:40.652: INFO:
Nov 18 05:47:42.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:42.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:42.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:42.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
Nov 18 05:47:42.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:42.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:42.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:42.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:42.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:42.624: INFO:
Nov 18 05:47:44.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:44.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:44.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:44.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
Nov 18 05:47:44.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:44.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:44.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:44.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:44.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:44.625: INFO:
Nov 18 05:47:46.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:46.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:46.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:46.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
Nov 18 05:47:46.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:46.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:46.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:46.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:46.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:46.625: INFO:
Nov 18 05:47:48.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:48.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:48.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:48.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
Nov 18 05:47:48.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:48.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:48.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:48.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:48.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:48.627: INFO:
Nov 18 05:47:50.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:50.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:50.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:50.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
Nov 18 05:47:50.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:50.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:50.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:50.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:50.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:50.628: INFO:
Nov 18 05:47:52.623: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:52.623: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:52.623: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:52.623: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
Nov 18 05:47:52.623: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:52.623: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:52.623: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:52.623: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:52.623: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:52.623: INFO:
Nov 18 05:47:54.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:54.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:54.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:54.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
Nov 18 05:47:54.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:54.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:54.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:54.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:54.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:54.632: INFO:
Nov 18 05:47:56.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:56.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:56.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:56.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
Nov 18 05:47:56.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:56.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:56.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:56.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:56.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:56.624: INFO:
Nov 18 05:47:58.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:58.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:58.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:47:58.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
Nov 18 05:47:58.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:47:58.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:47:58.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:58.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:58.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:47:58.626: INFO:
Nov 18 05:48:00.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:00.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:00.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:00.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
Nov 18 05:48:00.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:00.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:00.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:00.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:00.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:00.625: INFO:
Nov 18 05:48:02.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:02.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:02.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:02.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
Nov 18 05:48:02.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:02.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:02.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:02.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:02.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:02.625: INFO:
Nov 18 05:48:04.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:04.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:04.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:04.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
Nov 18 05:48:04.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:04.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:04.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:04.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:04.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:04.625: INFO:
Nov 18 05:48:06.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:06.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:06.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:06.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
Nov 18 05:48:06.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:06.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:06.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:06.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:06.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:06.625: INFO:
Nov 18 05:48:08.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:08.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:08.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:08.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
Nov 18 05:48:08.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:08.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:08.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:08.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:08.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:08.625: INFO:
Nov 18 05:48:10.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:10.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:10.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:10.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
Nov 18 05:48:10.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:10.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:10.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:10.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:10.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:10.630: INFO:
Nov 18 05:48:12.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:12.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:12.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:12.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
Nov 18 05:48:12.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:12.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:12.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:12.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:12.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:12.627: INFO:
Nov 18 05:48:14.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:14.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:14.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:14.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
Nov 18 05:48:14.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:14.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:14.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:14.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:14.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:14.624: INFO:
Nov 18 05:48:16.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:16.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:16.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:16.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
Nov 18 05:48:16.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:16.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:16.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:16.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:16.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:16.624: INFO:
Nov 18 05:48:18.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:18.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:18.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:18.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
Nov 18 05:48:18.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:18.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:18.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:18.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:18.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:18.627: INFO:
Nov 18 05:48:20.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:20.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:20.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:20.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
Nov 18 05:48:20.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:20.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:20.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:20.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:20.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:20.625: INFO:
Nov 18 05:48:22.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:22.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:22.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:22.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
Nov 18 05:48:22.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:22.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:22.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:22.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:22.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:22.625: INFO:
Nov 18 05:48:24.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:24.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:24.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:24.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
Nov 18 05:48:24.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:24.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:24.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:24.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:24.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:24.625: INFO:
Nov 18 05:48:26.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:26.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:26.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:26.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
Nov 18 05:48:26.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:26.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:26.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:26.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:26.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:26.626: INFO:
Nov 18 05:48:28.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:28.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:28.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:28.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
Nov 18 05:48:28.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:28.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:28.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:28.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:28.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:28.625: INFO:
Nov 18 05:48:30.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:30.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:30.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:30.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
Nov 18 05:48:30.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:30.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:30.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:30.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:30.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:30.631: INFO:
Nov 18 05:48:32.623: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:32.623: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:32.623: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:32.623: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
Nov 18 05:48:32.623: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:32.623: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:32.623: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:32.623: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:32.623: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:32.623: INFO:
Nov 18 05:48:34.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:34.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:34.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:34.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
Nov 18 05:48:34.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:34.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:34.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:34.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:34.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:34.626: INFO:
Nov 18 05:48:36.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:36.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:36.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:36.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
Nov 18 05:48:36.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:36.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:36.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:36.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:36.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:36.624: INFO:
Nov 18 05:48:38.623: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:38.623: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:38.623: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:38.623: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
Nov 18 05:48:38.623: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:38.623: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:38.623: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:38.623: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:38.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:38.624: INFO:
Nov 18 05:48:40.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:40.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:40.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:40.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
Nov 18 05:48:40.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:40.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:40.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:40.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:40.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:40.625: INFO:
Nov 18 05:48:42.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:42.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:42.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:42.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
Nov 18 05:48:42.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:42.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:42.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:42.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:42.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:42.626: INFO:
Nov 18 05:48:44.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:44.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:44.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:44.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
Nov 18 05:48:44.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:44.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:44.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:44.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:44.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:44.630: INFO:
Nov 18 05:48:46.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:46.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:46.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:46.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
Nov 18 05:48:46.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:46.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:46.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:46.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:46.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:46.627: INFO:
Nov 18 05:48:48.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:48.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:48.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:48.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
Nov 18 05:48:48.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:48.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:48.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:48.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:48.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:48.624: INFO:
Nov 18 05:48:50.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:50.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:50.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:50.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
Nov 18 05:48:50.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:50.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:50.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:50.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:50.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:50.625: INFO:
Nov 18 05:48:52.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:52.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:52.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:52.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
Nov 18 05:48:52.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:52.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:52.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:52.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:52.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:52.624: INFO:
Nov 18 05:48:54.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:54.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:54.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:54.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
Nov 18 05:48:54.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:54.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:54.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:54.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:54.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:54.630: INFO:
Nov 18 05:48:56.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:56.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:56.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:56.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
Nov 18 05:48:56.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:56.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:56.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:56.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:56.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:56.626: INFO:
Nov 18 05:48:58.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:58.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:58.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:48:58.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
Nov 18 05:48:58.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:48:58.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:48:58.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:58.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:58.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:48:58.629: INFO:
Nov 18 05:49:00.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:00.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:00.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:00.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
Nov 18 05:49:00.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:00.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:00.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:00.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:00.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:00.626: INFO:
Nov 18 05:49:02.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:02.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:02.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:02.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
Nov 18 05:49:02.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:02.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:02.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:02.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:02.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:02.625: INFO:
Nov 18 05:49:04.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:04.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:04.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:04.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
Nov 18 05:49:04.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:04.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:04.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:04.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:04.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:04.624: INFO:
Nov 18 05:49:06.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:06.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:06.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:06.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
Nov 18 05:49:06.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:06.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:06.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:06.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:06.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:06.632: INFO:
Nov 18 05:49:08.637: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:08.637: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:08.637: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:08.637: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
Nov 18 05:49:08.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:08.637: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:08.637: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:08.637: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:08.637: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:08.637: INFO:
Nov 18 05:49:10.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:10.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:10.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:10.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
Nov 18 05:49:10.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:10.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:10.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:10.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:10.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:10.628: INFO:
Nov 18 05:49:12.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:12.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:12.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:12.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
Nov 18 05:49:12.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:12.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:12.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:12.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:12.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:12.625: INFO:
Nov 18 05:49:14.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:14.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:14.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:14.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
Nov 18 05:49:14.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:14.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:14.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:14.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:14.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:14.624: INFO:
Nov 18 05:49:16.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:16.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:16.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:16.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
Nov 18 05:49:16.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:16.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:16.633: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:16.633: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:16.633: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:16.633: INFO:
Nov 18 05:49:18.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:18.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:18.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:18.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
Nov 18 05:49:18.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:18.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:18.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:18.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:18.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:18.624: INFO:
Nov 18 05:49:20.623: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:20.623: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:20.623: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:20.623: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
Nov 18 05:49:20.623: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:20.623: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:20.623: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:20.623: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:20.623: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:20.623: INFO:
Nov 18 05:49:22.633: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:22.633: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:22.633: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:22.633: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
Nov 18 05:49:22.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:22.633: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:22.633: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:22.633: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:22.633: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:22.633: INFO:
Nov 18 05:49:24.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:24.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:24.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:24.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
Nov 18 05:49:24.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:24.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:24.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:24.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:24.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:24.625: INFO:
Nov 18 05:49:26.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:26.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:26.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:26.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
Nov 18 05:49:26.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:26.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:26.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:26.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:26.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:26.629: INFO:
Nov 18 05:49:28.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:28.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:28.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:28.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
Nov 18 05:49:28.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:28.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:28.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:28.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:28.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:28.625: INFO:
Nov 18 05:49:30.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:30.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:30.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:30.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
Nov 18 05:49:30.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:30.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:30.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:30.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:30.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:30.625: INFO:
Nov 18 05:49:32.637: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:32.637: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:32.637: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:32.637: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
Nov 18 05:49:32.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:32.637: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:32.637: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:32.637: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:32.637: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:32.637: INFO:
Nov 18 05:49:34.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:34.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:34.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:34.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
Nov 18 05:49:34.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:34.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:34.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:34.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:34.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:34.624: INFO:
Nov 18 05:49:36.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:36.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:36.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:36.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
Nov 18 05:49:36.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:36.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:36.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:36.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:36.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:36.626: INFO:
Nov 18 05:49:38.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:38.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:38.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:38.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
Nov 18 05:49:38.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:38.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:38.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:38.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:38.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:38.629: INFO:
Nov 18 05:49:40.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:40.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:40.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:40.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
Nov 18 05:49:40.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:40.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:40.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:40.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:40.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:40.631: INFO:
Nov 18 05:49:42.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:42.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:42.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:42.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
Nov 18 05:49:42.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:42.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:42.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:42.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:42.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:42.625: INFO:
Nov 18 05:49:44.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:44.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:44.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:44.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
Nov 18 05:49:44.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:44.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:44.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:44.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:44.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:44.628: INFO:
Nov 18 05:49:46.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:46.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:46.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:46.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
Nov 18 05:49:46.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:46.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:46.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:46.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:46.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:46.626: INFO:
Nov 18 05:49:48.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:48.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:48.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:48.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
Nov 18 05:49:48.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:48.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:48.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:48.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:48.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:48.624: INFO:
Nov 18 05:49:50.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:50.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:50.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:50.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
Nov 18 05:49:50.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:50.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:50.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:50.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:50.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:50.625: INFO:
Nov 18 05:49:52.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:52.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:52.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:52.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
Nov 18 05:49:52.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:52.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:52.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:52.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:52.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:52.624: INFO:
Nov 18 05:49:54.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:54.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:54.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:54.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
Nov 18 05:49:54.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:54.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:54.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:54.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:54.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:54.625: INFO:
Nov 18 05:49:56.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:56.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:56.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:56.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
Nov 18 05:49:56.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:56.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:56.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:56.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:56.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:56.624: INFO:
Nov 18 05:49:58.623: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:58.623: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:58.623: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:49:58.623: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
Nov 18 05:49:58.623: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:49:58.623: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:49:58.623: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:58.623: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:58.623: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:49:58.623: INFO:
Nov 18 05:50:00.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:00.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:00.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:00.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
Nov 18 05:50:00.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:00.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:00.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:00.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:00.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:00.626: INFO:
Nov 18 05:50:02.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:02.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:02.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:02.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
Nov 18 05:50:02.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:02.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:02.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:02.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:02.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:02.627: INFO:
Nov 18 05:50:04.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:04.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:04.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:04.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
Nov 18 05:50:04.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:04.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:04.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:04.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:04.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:04.625: INFO:
Nov 18 05:50:06.733: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:06.733: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:06.733: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:06.733: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
Nov 18 05:50:06.733: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:06.733: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:06.733: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:06.733: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:06.733: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:06.733: INFO:
Nov 18 05:50:08.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:08.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:08.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:08.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
Nov 18 05:50:08.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:08.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:08.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:08.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:08.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:08.626: INFO:
Nov 18 05:50:10.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:10.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:10.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:10.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
Nov 18 05:50:10.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:10.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:10.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:10.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:10.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:10.627: INFO:
Nov 18 05:50:12.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:12.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:12.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:12.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
Nov 18 05:50:12.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:12.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:12.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:12.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:12.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:12.626: INFO:
Nov 18 05:50:14.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:14.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:14.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:14.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
Nov 18 05:50:14.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:14.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:14.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:14.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:14.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:14.625: INFO:
Nov 18 05:50:16.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:16.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:16.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:16.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
Nov 18 05:50:16.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:16.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:16.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:16.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:16.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:16.626: INFO:
Nov 18 05:50:18.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:18.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:18.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:18.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
Nov 18 05:50:18.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:18.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:18.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:18.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:18.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:18.624: INFO:
Nov 18 05:50:20.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:20.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:20.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:20.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
Nov 18 05:50:20.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:20.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:20.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:20.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:20.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:20.625: INFO:
Nov 18 05:50:22.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:22.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:22.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:22.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
Nov 18 05:50:22.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:22.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:22.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:22.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:22.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:22.624: INFO:
Nov 18 05:50:24.633: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:24.633: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:24.633: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:24.633: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
Nov 18 05:50:24.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:24.633: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:24.633: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:24.633: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:24.633: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:24.633: INFO:
Nov 18 05:50:26.624: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:26.624: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:26.624: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:26.624: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
Nov 18 05:50:26.624: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:26.624: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:26.624: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:26.624: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:26.624: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:26.624: INFO:
Nov 18 05:50:28.634: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:28.634: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:28.634: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:28.634: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
Nov 18 05:50:28.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:28.634: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:28.634: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:28.634: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:28.634: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:28.634: INFO:
Nov 18 05:50:30.635: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:30.635: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:30.635: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:30.635: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
Nov 18 05:50:30.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:30.635: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:30.635: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:30.635: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:30.635: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:30.635: INFO:
Nov 18 05:50:32.633: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:32.633: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:32.633: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:32.633: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
Nov 18 05:50:32.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:32.633: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:32.633: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:32.633: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:32.633: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:32.633: INFO:
Nov 18 05:50:34.647: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:34.647: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:34.647: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:34.647: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
Nov 18 05:50:34.647: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:34.647: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:34.647: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:34.647: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:34.647: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:34.647: INFO:
Nov 18 05:50:36.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:36.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:36.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:36.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
Nov 18 05:50:36.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:36.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:36.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:36.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:36.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:36.629: INFO:
Nov 18 05:50:38.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:38.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:38.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:38.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
Nov 18 05:50:38.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:38.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:38.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:38.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:38.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:38.631: INFO:
Nov 18 05:50:40.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:40.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:40.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:40.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
Nov 18 05:50:40.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:40.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:40.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:40.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:40.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:40.631: INFO:
Nov 18 05:50:42.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:42.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:42.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:42.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
Nov 18 05:50:42.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:42.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:42.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:42.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:42.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:42.628: INFO:
Nov 18 05:50:44.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:44.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:44.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:44.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
Nov 18 05:50:44.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:44.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:44.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:44.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:44.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:44.629: INFO:
Nov 18 05:50:46.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:46.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:46.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:46.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
Nov 18 05:50:46.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:46.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:46.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:46.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:46.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:46.632: INFO:
Nov 18 05:50:48.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:48.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:48.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:48.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
Nov 18 05:50:48.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:48.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:48.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:48.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:48.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:48.631: INFO:
Nov 18 05:50:50.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:50.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:50.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:50.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
Nov 18 05:50:50.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:50.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:50.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:50.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:50.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:50.627: INFO:
Nov 18 05:50:52.741: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:52.741: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:52.741: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:52.741: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
Nov 18 05:50:52.741: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:52.741: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:52.741: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:52.741: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:52.741: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:52.741: INFO:
Nov 18 05:50:54.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:54.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:54.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:54.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
Nov 18 05:50:54.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:54.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:54.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:54.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:54.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:54.632: INFO:
Nov 18 05:50:56.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:56.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:56.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:56.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
Nov 18 05:50:56.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:56.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:56.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:56.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:56.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:56.628: INFO:
Nov 18 05:50:58.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:58.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:58.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:50:58.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
Nov 18 05:50:58.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:50:58.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:50:58.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:58.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:58.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:50:58.632: INFO:
Nov 18 05:51:00.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:00.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:00.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:00.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
Nov 18 05:51:00.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:00.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:00.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:00.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:00.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:00.631: INFO:
Nov 18 05:51:02.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:02.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:02.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:02.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
Nov 18 05:51:02.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:02.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:02.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:02.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:02.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:02.627: INFO:
Nov 18 05:51:04.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:04.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:04.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:04.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
Nov 18 05:51:04.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:04.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:04.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:04.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:04.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:04.630: INFO:
Nov 18 05:51:06.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:06.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:06.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:06.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
Nov 18 05:51:06.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:06.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:06.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:06.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:06.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:06.627: INFO:
Nov 18 05:51:08.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:08.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:08.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:08.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
Nov 18 05:51:08.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:08.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:08.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:08.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:08.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:08.630: INFO:
Nov 18 05:51:10.635: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:10.635: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:10.635: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:10.635: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
Nov 18 05:51:10.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:10.635: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:10.635: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:10.635: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:10.635: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:10.635: INFO:
Nov 18 05:51:12.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:12.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:12.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:12.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
Nov 18 05:51:12.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:12.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:12.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:12.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:12.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:12.629: INFO:
Nov 18 05:51:14.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:14.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:14.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:14.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
Nov 18 05:51:14.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:14.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:14.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:14.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:14.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:14.632: INFO:
Nov 18 05:51:16.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:16.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:16.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:16.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
Nov 18 05:51:16.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:16.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:16.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:16.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:16.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:16.627: INFO:
Nov 18 05:51:18.634: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:18.634: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:18.634: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:18.634: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
Nov 18 05:51:18.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:18.634: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:18.634: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:18.634: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:18.634: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:18.634: INFO:
Nov 18 05:51:20.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:20.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:20.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:20.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
Nov 18 05:51:20.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:20.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:20.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:20.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:20.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:20.629: INFO:
Nov 18 05:51:22.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:22.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:22.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:22.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
Nov 18 05:51:22.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:22.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:22.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:22.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:22.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:22.632: INFO:
Nov 18 05:51:24.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:24.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:24.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:24.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
Nov 18 05:51:24.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:24.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:24.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:24.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:24.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:24.631: INFO:
Nov 18 05:51:26.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:26.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:26.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:26.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
Nov 18 05:51:26.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:26.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:26.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:26.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:26.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:26.631: INFO:
Nov 18 05:51:28.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:28.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:28.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:28.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
Nov 18 05:51:28.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:28.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:28.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:28.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:28.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:28.629: INFO:
Nov 18 05:51:30.633: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:30.633: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:30.633: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:30.633: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
Nov 18 05:51:30.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:30.633: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:30.633: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:30.633: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:30.633: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:30.634: INFO:
Nov 18 05:51:32.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:32.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:32.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:32.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
Nov 18 05:51:32.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:32.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:32.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:32.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:32.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:32.628: INFO:
Nov 18 05:51:34.634: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:34.634: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:34.634: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:34.634: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
Nov 18 05:51:34.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:34.634: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:34.634: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:34.634: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:34.634: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:34.634: INFO:
Nov 18 05:51:36.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:36.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:36.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:36.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
Nov 18 05:51:36.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:36.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:36.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:36.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:36.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:36.632: INFO:
Nov 18 05:51:38.633: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:38.633: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:38.633: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:38.633: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
Nov 18 05:51:38.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:38.633: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:38.633: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:38.633: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:38.633: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:38.633: INFO:
Nov 18 05:51:40.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:40.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:40.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:40.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
Nov 18 05:51:40.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:40.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:40.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:40.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:40.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:40.630: INFO:
Nov 18 05:51:42.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:42.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:42.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:42.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
Nov 18 05:51:42.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:42.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:42.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:42.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:42.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:42.632: INFO:
Nov 18 05:51:44.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:44.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:44.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:44.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
Nov 18 05:51:44.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:44.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:44.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:44.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:44.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:44.631: INFO:
Nov 18 05:51:46.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:46.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:46.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:46.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
Nov 18 05:51:46.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:46.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:46.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:46.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:46.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:46.631: INFO:
Nov 18 05:51:48.635: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:48.635: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:48.635: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:48.635: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
Nov 18 05:51:48.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:48.635: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:48.635: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:48.635: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:48.635: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:48.635: INFO:
Nov 18 05:51:50.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:50.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:50.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:50.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
Nov 18 05:51:50.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:50.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:50.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:50.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:50.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:50.631: INFO:
Nov 18 05:51:52.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:52.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:52.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:52.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
Nov 18 05:51:52.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:52.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:52.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:52.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:52.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:52.630: INFO:
Nov 18 05:51:54.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:54.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:54.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:54.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
Nov 18 05:51:54.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:54.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:54.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:54.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:54.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:54.631: INFO:
Nov 18 05:51:56.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:56.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:56.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:56.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
Nov 18 05:51:56.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:56.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:56.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:56.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:56.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:56.629: INFO:
Nov 18 05:51:58.633: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:58.633: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:58.633: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:51:58.633: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
Nov 18 05:51:58.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:51:58.633: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:51:58.633: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:58.633: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:58.633: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:51:58.633: INFO:
Nov 18 05:52:00.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:00.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:00.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:00.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
Nov 18 05:52:00.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:00.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:00.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:00.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:00.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:00.631: INFO:
Nov 18 05:52:02.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:02.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:02.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:02.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
Nov 18 05:52:02.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:02.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:02.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:02.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:02.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:02.632: INFO:
Nov 18 05:52:04.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:04.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:04.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:04.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
Nov 18 05:52:04.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:04.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:04.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:04.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:04.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:04.631: INFO:
Nov 18 05:52:06.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:06.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:06.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:06.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
Nov 18 05:52:06.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:06.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:06.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:06.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:06.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:06.632: INFO:
Nov 18 05:52:08.633: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:08.633: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:08.633: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:08.633: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
Nov 18 05:52:08.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:08.633: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:08.633: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:08.633: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:08.633: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:08.633: INFO:
Nov 18 05:52:10.633: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:10.633: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:10.633: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:10.633: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
Nov 18 05:52:10.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:10.633: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:10.633: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:10.633: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:10.633: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:10.633: INFO:
Nov 18 05:52:12.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:12.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:12.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:12.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
Nov 18 05:52:12.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:12.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:12.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:12.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:12.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:12.631: INFO:
Nov 18 05:52:14.643: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:14.643: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:14.643: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:14.643: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
Nov 18 05:52:14.643: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:14.643: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:14.643: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:14.643: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:14.643: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:14.643: INFO:
Nov 18 05:52:16.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:16.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:16.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:16.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
Nov 18 05:52:16.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:16.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:16.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:16.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:16.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:16.632: INFO:
Nov 18 05:52:18.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:18.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:18.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:18.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
Nov 18 05:52:18.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:18.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:18.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:18.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:18.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:18.630: INFO:
Nov 18 05:52:20.634: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:20.634: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:20.634: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:20.634: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
Nov 18 05:52:20.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:20.634: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:20.634: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:20.634: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:20.634: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:20.634: INFO:
Nov 18 05:52:22.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:22.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:22.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:22.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
Nov 18 05:52:22.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:22.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:22.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:22.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:22.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:22.630: INFO:
Nov 18 05:52:24.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:24.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:24.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:24.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
Nov 18 05:52:24.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:24.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:24.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:24.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:24.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:24.629: INFO:
Nov 18 05:52:26.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:26.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:26.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:26.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
Nov 18 05:52:26.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:26.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:26.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:26.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:26.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:26.627: INFO:
Nov 18 05:52:28.642: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:28.642: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:28.642: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:28.642: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
Nov 18 05:52:28.642: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:28.642: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:28.642: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:28.642: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:28.642: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:28.642: INFO:
Nov 18 05:52:30.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:30.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:30.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:30.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
Nov 18 05:52:30.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:30.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:30.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:30.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:30.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:30.629: INFO:
Nov 18 05:52:32.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:32.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:32.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:32.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
Nov 18 05:52:32.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:32.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:32.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:32.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:32.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:32.630: INFO:
Nov 18 05:52:34.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:34.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:34.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:34.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
Nov 18 05:52:34.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:34.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:34.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:34.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:34.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:34.632: INFO:
Nov 18 05:52:36.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:36.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:36.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:36.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
Nov 18 05:52:36.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:36.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:36.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:36.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:36.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:36.631: INFO:
Nov 18 05:52:38.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:38.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:38.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:38.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
Nov 18 05:52:38.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:38.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:38.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:38.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:38.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:38.631: INFO:
Nov 18 05:52:40.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:40.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:40.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:40.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
Nov 18 05:52:40.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:40.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:40.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:40.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:40.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:40.629: INFO:
Nov 18 05:52:42.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:42.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:42.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:42.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
Nov 18 05:52:42.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:42.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:42.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:42.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:42.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:42.629: INFO:
Nov 18 05:52:44.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:44.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:44.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:44.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
Nov 18 05:52:44.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:44.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:44.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:44.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:44.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:44.629: INFO:
Nov 18 05:52:46.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:46.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:46.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:46.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
Nov 18 05:52:46.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:46.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:46.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:46.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:46.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:46.631: INFO:
Nov 18 05:52:48.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:48.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:48.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:48.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
Nov 18 05:52:48.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:48.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:48.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:48.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:48.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:48.629: INFO:
Nov 18 05:52:50.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:50.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:50.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:50.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
Nov 18 05:52:50.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:50.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:50.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:50.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:50.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:50.632: INFO:
Nov 18 05:52:52.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:52.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:52.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:52.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
Nov 18 05:52:52.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:52.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:52.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:52.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:52.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:52.631: INFO:
Nov 18 05:52:54.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:54.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:54.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:54.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
Nov 18 05:52:54.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:54.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:54.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:54.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:54.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:54.629: INFO:
Nov 18 05:52:56.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:56.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:56.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:56.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
Nov 18 05:52:56.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:56.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:56.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:56.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:56.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:56.630: INFO:
Nov 18 05:52:58.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:58.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:58.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:52:58.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
Nov 18 05:52:58.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:52:58.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:52:58.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:58.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:58.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:52:58.629: INFO:
Nov 18 05:53:00.637: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:00.637: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:00.637: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:00.638: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
Nov 18 05:53:00.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:00.638: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:00.638: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:00.638: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:00.638: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:00.638: INFO:
Nov 18 05:53:02.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:02.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:02.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:02.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
Nov 18 05:53:02.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:02.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:02.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:02.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:02.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:02.631: INFO:
Nov 18 05:53:04.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:04.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:04.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:04.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
Nov 18 05:53:04.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:04.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:04.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:04.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:04.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:04.632: INFO:
Nov 18 05:53:06.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:06.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:06.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:06.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
Nov 18 05:53:06.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:06.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:06.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:06.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:06.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:06.629: INFO:
Nov 18 05:53:08.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:08.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:08.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:08.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
Nov 18 05:53:08.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:08.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:08.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:08.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:08.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:08.630: INFO:
Nov 18 05:53:10.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:10.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:10.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:10.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
Nov 18 05:53:10.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:10.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:10.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:10.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:10.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:10.628: INFO:
Nov 18 05:53:12.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:12.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:12.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:12.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
Nov 18 05:53:12.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:12.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:12.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:12.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:12.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:12.629: INFO:
Nov 18 05:53:14.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:14.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:14.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:14.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
Nov 18 05:53:14.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:14.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:14.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:14.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:14.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:14.628: INFO:
Nov 18 05:53:16.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:16.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:16.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:16.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
Nov 18 05:53:16.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:16.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:16.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:16.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:16.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:16.630: INFO:
Nov 18 05:53:18.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:18.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:18.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:18.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
Nov 18 05:53:18.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:18.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:18.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:18.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:18.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:18.630: INFO:
Nov 18 05:53:20.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:20.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:20.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:20.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
Nov 18 05:53:20.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:20.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:20.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:20.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:20.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:20.628: INFO:
Nov 18 05:53:22.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:22.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:22.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:22.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
Nov 18 05:53:22.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:22.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:22.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:22.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:22.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:22.631: INFO:
Nov 18 05:53:24.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:24.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:24.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:24.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
Nov 18 05:53:24.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:24.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:24.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:24.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:24.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:24.630: INFO:
Nov 18 05:53:26.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:26.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:26.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:26.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
Nov 18 05:53:26.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:26.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:26.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:26.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:26.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:26.628: INFO:
Nov 18 05:53:28.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:28.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:28.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:28.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
Nov 18 05:53:28.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:28.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:28.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:28.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:28.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:28.632: INFO:
Nov 18 05:53:30.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:30.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:30.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:30.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
Nov 18 05:53:30.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:30.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:30.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:30.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:30.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:30.631: INFO:
Nov 18 05:53:32.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:32.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:32.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:32.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
Nov 18 05:53:32.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:32.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:32.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:32.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:32.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:32.627: INFO:
Nov 18 05:53:34.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:34.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:34.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:34.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
Nov 18 05:53:34.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:34.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:34.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:34.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:34.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:34.630: INFO:
Nov 18 05:53:36.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:36.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:36.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:36.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
Nov 18 05:53:36.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:36.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:36.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:36.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:36.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:36.629: INFO:
Nov 18 05:53:38.633: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:38.633: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:38.633: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:38.633: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
Nov 18 05:53:38.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:38.633: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:38.633: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:38.633: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:38.633: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:38.633: INFO:
Nov 18 05:53:40.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:40.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:40.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:40.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
Nov 18 05:53:40.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:40.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:40.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:40.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:40.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:40.631: INFO:
Nov 18 05:53:42.634: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:42.634: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:42.634: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:42.634: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
Nov 18 05:53:42.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:42.634: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:42.634: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:42.634: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:42.634: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:42.634: INFO:
Nov 18 05:53:44.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:44.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:44.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:44.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
Nov 18 05:53:44.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:44.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:44.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:44.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:44.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:44.632: INFO:
Nov 18 05:53:46.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:46.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:46.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:46.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
Nov 18 05:53:46.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:46.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:46.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:46.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:46.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:46.627: INFO:
Nov 18 05:53:48.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:48.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:48.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:48.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
Nov 18 05:53:48.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:48.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:48.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:48.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:48.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:48.632: INFO:
Nov 18 05:53:50.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:50.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:50.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:50.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
Nov 18 05:53:50.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:50.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:50.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:50.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:50.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:50.628: INFO:
Nov 18 05:53:52.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:52.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:52.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:52.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
Nov 18 05:53:52.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:52.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:52.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:52.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:52.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:52.631: INFO:
Nov 18 05:53:54.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:54.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:54.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:54.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
Nov 18 05:53:54.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:54.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:54.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:54.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:54.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:54.630: INFO:
Nov 18 05:53:56.634: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:56.634: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:56.634: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:56.634: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
Nov 18 05:53:56.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:56.634: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:56.634: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:56.634: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:56.634: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:56.634: INFO:
Nov 18 05:53:58.635: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:58.635: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:58.635: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:53:58.635: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
Nov 18 05:53:58.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:53:58.635: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:53:58.635: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:58.635: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:58.635: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:53:58.635: INFO:
Nov 18 05:54:00.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:00.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:00.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:00.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
Nov 18 05:54:00.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:00.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:00.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:00.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:00.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:00.629: INFO:
Nov 18 05:54:02.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:02.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:02.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:02.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
Nov 18 05:54:02.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:02.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:02.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:02.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:02.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:02.630: INFO:
Nov 18 05:54:04.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:04.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:04.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:04.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
Nov 18 05:54:04.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:04.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:04.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:04.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:04.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:04.629: INFO:
Nov 18 05:54:06.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:06.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:06.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:06.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
Nov 18 05:54:06.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:06.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:06.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:06.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:06.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:06.628: INFO:
Nov 18 05:54:08.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:08.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:08.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:08.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
Nov 18 05:54:08.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:08.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:08.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:08.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:08.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:08.630: INFO:
Nov 18 05:54:10.639: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:10.639: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:10.639: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:10.639: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
Nov 18 05:54:10.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:10.639: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:10.639: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:10.639: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:10.639: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:10.639: INFO:
Nov 18 05:54:12.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:12.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:12.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:12.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
Nov 18 05:54:12.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:12.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:12.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:12.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:12.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:12.631: INFO:
Nov 18 05:54:14.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:14.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:14.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:14.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
Nov 18 05:54:14.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:14.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:14.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:14.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:14.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:14.630: INFO:
Nov 18 05:54:16.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:16.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:16.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:16.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
Nov 18 05:54:16.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:16.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:16.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:16.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:16.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:16.629: INFO:
Nov 18 05:54:18.636: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:18.636: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:18.636: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:18.636: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
Nov 18 05:54:18.636: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:18.636: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:18.636: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:18.636: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:18.636: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:18.636: INFO:
Nov 18 05:54:20.625: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:20.625: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:20.625: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:20.625: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
Nov 18 05:54:20.625: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:20.625: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:20.625: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:20.625: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:20.625: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:20.625: INFO:
Nov 18 05:54:22.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:22.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:22.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:22.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
Nov 18 05:54:22.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:22.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:22.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:22.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:22.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:22.631: INFO:
Nov 18 05:54:24.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:24.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:24.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:24.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
Nov 18 05:54:24.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:24.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:24.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:24.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:24.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:24.630: INFO:
Nov 18 05:54:26.626: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:26.626: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:26.626: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:26.626: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
Nov 18 05:54:26.626: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:26.626: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:26.626: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:26.626: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:26.626: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:26.626: INFO:
Nov 18 05:54:28.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:28.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:28.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:28.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
Nov 18 05:54:28.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:28.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:28.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:28.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:28.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:28.632: INFO:
Nov 18 05:54:30.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:30.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:30.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:30.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
Nov 18 05:54:30.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:30.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:30.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:30.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:30.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:30.629: INFO:
Nov 18 05:54:32.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:32.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:32.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:32.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
Nov 18 05:54:32.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:32.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:32.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:32.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:32.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:32.632: INFO:
Nov 18 05:54:34.635: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:34.635: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:34.635: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:34.635: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
Nov 18 05:54:34.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:34.635: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:34.635: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:34.635: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:34.635: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:34.635: INFO:
Nov 18 05:54:36.638: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:36.638: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:36.638: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:36.638: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
Nov 18 05:54:36.638: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:36.638: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:36.638: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:36.638: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:36.638: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:36.638: INFO:
Nov 18 05:54:38.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:38.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:38.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:38.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
Nov 18 05:54:38.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:38.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:38.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:38.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:38.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:38.631: INFO:
Nov 18 05:54:40.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:40.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:40.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:40.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
Nov 18 05:54:40.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:40.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:40.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:40.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:40.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:40.631: INFO:
Nov 18 05:54:42.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:42.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:42.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:42.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
Nov 18 05:54:42.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:42.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:42.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:42.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:42.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:42.628: INFO:
Nov 18 05:54:44.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:44.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:44.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:44.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
Nov 18 05:54:44.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:44.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:44.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:44.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:44.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:44.632: INFO:
Nov 18 05:54:46.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:46.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:46.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:46.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
Nov 18 05:54:46.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:46.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:46.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:46.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:46.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:46.628: INFO:
Nov 18 05:54:48.639: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:48.639: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:48.639: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:48.639: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
Nov 18 05:54:48.639: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:48.639: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:48.639: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:48.639: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:48.639: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:48.639: INFO:
Nov 18 05:54:50.635: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:50.635: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:50.635: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:50.635: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
Nov 18 05:54:50.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:50.635: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:50.635: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:50.635: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:50.635: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:50.635: INFO:
Nov 18 05:54:52.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:52.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:52.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:52.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
Nov 18 05:54:52.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:52.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:52.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:52.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:52.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:52.629: INFO:
Nov 18 05:54:54.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:54.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:54.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:54.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
Nov 18 05:54:54.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:54.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:54.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:54.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:54.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:54.630: INFO:
Nov 18 05:54:56.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:56.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:56.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:56.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
Nov 18 05:54:56.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:56.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:56.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:56.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:56.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:56.627: INFO:
Nov 18 05:54:58.633: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:58.633: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:58.633: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:54:58.633: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
Nov 18 05:54:58.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:54:58.633: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:54:58.633: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:58.633: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:58.633: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:54:58.633: INFO:
Nov 18 05:55:00.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:00.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:00.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:00.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
Nov 18 05:55:00.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:00.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:00.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:00.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:00.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:00.630: INFO:
Nov 18 05:55:02.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:02.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:02.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:02.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
Nov 18 05:55:02.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:02.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:02.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:02.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:02.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:02.631: INFO:
Nov 18 05:55:04.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:04.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:04.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:04.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
Nov 18 05:55:04.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:04.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:04.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:04.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:04.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:04.629: INFO:
Nov 18 05:55:06.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:06.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:06.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:06.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
Nov 18 05:55:06.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:06.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:06.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:06.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:06.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:06.627: INFO:
Nov 18 05:55:08.634: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:08.634: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:08.634: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:08.634: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
Nov 18 05:55:08.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:08.634: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:08.634: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:08.634: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:08.634: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:08.634: INFO:
Nov 18 05:55:10.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:10.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:10.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:10.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
Nov 18 05:55:10.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:10.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:10.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:10.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:10.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:10.630: INFO:
Nov 18 05:55:12.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:12.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:12.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:12.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
Nov 18 05:55:12.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:12.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:12.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:12.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:12.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:12.629: INFO:
Nov 18 05:55:14.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:14.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:14.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:14.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
Nov 18 05:55:14.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:14.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:14.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:14.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:14.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:14.627: INFO:
Nov 18 05:55:16.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:16.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:16.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:16.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
Nov 18 05:55:16.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:16.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:16.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:16.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:16.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:16.627: INFO:
Nov 18 05:55:18.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:18.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:18.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:18.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
Nov 18 05:55:18.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:18.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:18.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:18.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:18.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:18.631: INFO:
Nov 18 05:55:20.635: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:20.635: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:20.635: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:20.635: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
Nov 18 05:55:20.635: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:20.635: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:20.635: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:20.635: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:20.635: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:20.635: INFO:
Nov 18 05:55:22.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:22.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:22.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:22.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
Nov 18 05:55:22.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:22.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:22.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:22.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:22.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:22.631: INFO:
Nov 18 05:55:24.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:24.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:24.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:24.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
Nov 18 05:55:24.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:24.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:24.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:24.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:24.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:24.629: INFO:
Nov 18 05:55:26.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:26.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:26.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:26.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
Nov 18 05:55:26.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:26.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:26.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:26.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:26.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:26.632: INFO:
Nov 18 05:55:28.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:28.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:28.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:28.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
Nov 18 05:55:28.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:28.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:28.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:28.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:28.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:28.630: INFO:
Nov 18 05:55:30.634: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:30.634: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:30.634: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:30.634: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
Nov 18 05:55:30.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:30.634: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:30.634: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:30.634: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:30.634: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:30.634: INFO:
Nov 18 05:55:32.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:32.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:32.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:32.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
Nov 18 05:55:32.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:32.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:32.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:32.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:32.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:32.629: INFO:
Nov 18 05:55:34.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:34.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:34.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:34.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
Nov 18 05:55:34.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:34.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:34.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:34.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:34.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:34.630: INFO:
Nov 18 05:55:36.637: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:36.637: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:36.637: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:36.637: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
Nov 18 05:55:36.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:36.637: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:36.637: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:36.637: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:36.638: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:36.638: INFO:
Nov 18 05:55:38.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:38.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:38.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:38.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
Nov 18 05:55:38.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:38.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:38.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:38.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:38.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:38.629: INFO:
Nov 18 05:55:40.637: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:40.637: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:40.637: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:40.637: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
Nov 18 05:55:40.637: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:40.637: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:40.637: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:40.637: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:40.637: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:40.637: INFO:
Nov 18 05:55:42.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:42.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:42.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:42.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
Nov 18 05:55:42.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:42.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:42.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:42.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:42.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:42.632: INFO:
Nov 18 05:55:44.627: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:44.627: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:44.627: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:44.627: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
Nov 18 05:55:44.627: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:44.627: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:44.627: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:44.627: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:44.627: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:44.627: INFO:
Nov 18 05:55:46.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:46.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:46.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:46.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
Nov 18 05:55:46.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:46.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:46.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:46.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:46.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:46.631: INFO:
Nov 18 05:55:48.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:48.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:48.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:48.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
Nov 18 05:55:48.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:48.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:48.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:48.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:48.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:48.629: INFO:
Nov 18 05:55:50.740: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:50.740: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:50.740: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:50.740: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
Nov 18 05:55:50.740: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:50.740: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:50.740: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:50.740: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:50.740: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:50.740: INFO:
Nov 18 05:55:52.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:52.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:52.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:52.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
Nov 18 05:55:52.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:52.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:52.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:52.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:52.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:52.632: INFO:
Nov 18 05:55:54.643: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:54.643: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:54.643: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:54.643: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
Nov 18 05:55:54.643: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:54.643: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:54.643: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:54.643: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:54.643: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:54.643: INFO:
Nov 18 05:55:56.634: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:56.634: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:56.634: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:56.634: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
Nov 18 05:55:56.634: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:56.634: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:56.634: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:56.634: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:56.634: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:56.634: INFO:
Nov 18 05:55:58.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:58.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:58.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:55:58.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
Nov 18 05:55:58.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:55:58.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:55:58.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:58.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:58.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:55:58.632: INFO:
Nov 18 05:56:00.631: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:00.631: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:00.631: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:00.631: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
Nov 18 05:56:00.631: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:56:00.631: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:56:00.631: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:00.631: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:00.631: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:00.631: INFO:
Nov 18 05:56:02.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:02.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:02.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:02.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
Nov 18 05:56:02.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:56:02.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:56:02.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:02.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:02.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:02.629: INFO:
Nov 18 05:56:04.628: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:04.628: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:04.628: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:04.628: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
Nov 18 05:56:04.628: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:56:04.628: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:56:04.628: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:04.628: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:04.628: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:04.628: INFO:
Nov 18 05:56:06.633: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:06.633: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:06.633: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:06.633: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
Nov 18 05:56:06.633: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:56:06.633: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:56:06.633: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:06.633: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:06.633: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:06.633: INFO:
Nov 18 05:56:08.640: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:08.640: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:08.640: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:08.640: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
Nov 18 05:56:08.640: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:56:08.640: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:56:08.640: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:08.640: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:08.640: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:08.640: INFO:
Nov 18 05:56:10.632: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:10.632: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:10.632: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:10.632: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
Nov 18 05:56:10.632: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:56:10.632: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:56:10.632: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:10.632: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:10.632: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:10.632: INFO:
Nov 18 05:56:12.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:12.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:12.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:12.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
Nov 18 05:56:12.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:56:12.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:56:12.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:12.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:12.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:12.630: INFO:
Nov 18 05:56:14.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:14.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:14.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:14.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
Nov 18 05:56:14.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:56:14.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:56:14.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:14.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:14.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:14.630: INFO:
Nov 18 05:56:16.630: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:16.630: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:16.630: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:16.630: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Nov 18 05:56:16.630: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:56:16.630: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:56:16.630: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:16.630: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:16.630: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:16.630: INFO:
Nov 18 05:56:18.754: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:18.754: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:18.754: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:18.754: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Nov 18 05:56:18.754: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:56:18.754: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:56:18.754: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:18.754: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:18.754: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:18.754: INFO:
Nov 18 05:56:20.629: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:20.629: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:20.629: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:20.629: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 18 05:56:20.629: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:56:20.629: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:56:20.629: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:20.629: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:20.629: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:20.629: INFO:
Nov 18 05:56:20.760: INFO: The status of Pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:20.760: INFO: The status of Pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:20.760: INFO: The status of Pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 18 05:56:20.760: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 18 05:56:20.760: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 18 05:56:20.760: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:56:20.760: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:20.760: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:20.760: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:20.760: INFO:
�[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m11/18/22 05:56:20.76�[0m
�[1mSTEP:�[0m Found 124 events. �[38;5;243m11/18/22 05:56:20.816�[0m
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:41:35 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-ucrofv-control-plane-rp9w6_cc4fcc99-9b8a-4961-b69f-6244ca64f65a became leader
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:41:36 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-ucrofv-control-plane-rp9w6_69e0a9fb-a8f2-4d1c-9e74-1233f93673a6 became leader
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:41:40 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-787d4945fb to 2
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:41:40 +0000 UTC - event for etcd-capz-conf-ucrofv-control-plane-rp9w6: {node-controller } NodeNotReady: Node is not ready
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:41:40 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-886lk
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:41:40 +0000 UTC - event for kube-proxy-886lk: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-886lk to capz-conf-ucrofv-control-plane-rp9w6
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:41:41 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-pw6s9
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:41:41 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-bm6bb
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:41:41 +0000 UTC - event for coredns-787d4945fb-bm6bb: {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 18 05:56:20.816: INFO: At 2022-11-18 05:41:41 +0000 UTC - event for coredns-787d4945fb-pw6s9: {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 18 05:56:20.816: INFO: At 2022-11-18 05:41:41 +0000 UTC - event for kube-proxy-886lk: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.30_86e8172755f0c3"
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:41:44 +0000 UTC - event for kube-proxy-886lk: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Created: Created container kube-proxy
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:41:44 +0000 UTC - event for kube-proxy-886lk: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.30_86e8172755f0c3" in 3.277723836s (3.277738737s including waiting)
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:41:45 +0000 UTC - event for kube-proxy-886lk: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Started: Started container kube-proxy
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:41:58 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:41:58 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-g8gwl
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:41:58 +0000 UTC - event for metrics-server-c9574f845-g8gwl: {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 18 05:56:20.816: INFO: At 2022-11-18 05:42:00 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:00 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-kw56f
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:00 +0000 UTC - event for calico-kube-controllers-657b584867-kw56f: {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 18 05:56:20.816: INFO: At 2022-11-18 05:42:00 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-99skp
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:00 +0000 UTC - event for calico-node-99skp: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-99skp to capz-conf-ucrofv-control-plane-rp9w6
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:01 +0000 UTC - event for calico-node-99skp: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:09 +0000 UTC - event for calico-node-99skp: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Started: Started container upgrade-ipam
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:09 +0000 UTC - event for calico-node-99skp: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 7.981381548s (7.981396532s including waiting)
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:09 +0000 UTC - event for calico-node-99skp: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Created: Created container upgrade-ipam
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:13 +0000 UTC - event for calico-node-99skp: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:13 +0000 UTC - event for calico-node-99skp: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Created: Created container install-cni
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:13 +0000 UTC - event for calico-node-99skp: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Started: Started container install-cni
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:16 +0000 UTC - event for calico-kube-controllers-657b584867-kw56f: {kubelet capz-conf-ucrofv-control-plane-rp9w6} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "7f7f74dd335e461646adf9aa002d5104a6890d5ad7559cba6d0e889c7958fff7": 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 18 05:56:20.816: INFO: At 2022-11-18 05:42:16 +0000 UTC - event for calico-kube-controllers-657b584867-kw56f: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-kw56f to capz-conf-ucrofv-control-plane-rp9w6
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:16 +0000 UTC - event for calico-node-99skp: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:16 +0000 UTC - event for coredns-787d4945fb-bm6bb: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-bm6bb to capz-conf-ucrofv-control-plane-rp9w6
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:16 +0000 UTC - event for coredns-787d4945fb-bm6bb: {kubelet capz-conf-ucrofv-control-plane-rp9w6} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "edc83da8b2ae3ce167178aaff6a61219eca1955b3ad7c78ee10a35f8b748f650": 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 18 05:56:20.816: INFO: At 2022-11-18 05:42:16 +0000 UTC - event for coredns-787d4945fb-pw6s9: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-pw6s9 to capz-conf-ucrofv-control-plane-rp9w6
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:16 +0000 UTC - event for coredns-787d4945fb-pw6s9: {kubelet capz-conf-ucrofv-control-plane-rp9w6} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "1b92935e97b2f97f8f39c34a6a89c62713b2bc877707ed7fd4e69b1467c2c88d": 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 18 05:56:20.816: INFO: At 2022-11-18 05:42:16 +0000 UTC - event for metrics-server-c9574f845-g8gwl: {kubelet capz-conf-ucrofv-control-plane-rp9w6} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "efcf3aed5281ceca772b2f59bd3748fa914a4ca50216b2dd8d0e3d0046af069b": 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 18 05:56:20.816: INFO: At 2022-11-18 05:42:16 +0000 UTC - event for metrics-server-c9574f845-g8gwl: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-g8gwl to capz-conf-ucrofv-control-plane-rp9w6
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:23 +0000 UTC - event for calico-node-99skp: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Started: Started container calico-node
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:23 +0000 UTC - event for calico-node-99skp: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 7.208327394s (7.208333192s including waiting)
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:23 +0000 UTC - event for calico-node-99skp: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Created: Created container calico-node
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:24 +0000 UTC - event for calico-node-99skp: {kubelet capz-conf-ucrofv-control-plane-rp9w6} 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 18 05:56:20.816: INFO: At 2022-11-18 05:42:27 +0000 UTC - event for coredns-787d4945fb-bm6bb: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:27 +0000 UTC - event for coredns-787d4945fb-bm6bb: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Created: Created container coredns
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:27 +0000 UTC - event for metrics-server-c9574f845-g8gwl: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:28 +0000 UTC - event for coredns-787d4945fb-bm6bb: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Started: Started container coredns
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:28 +0000 UTC - event for coredns-787d4945fb-bm6bb: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Unhealthy: Readiness probe failed: Get "http://192.168.175.129:8181/ready": dial tcp 192.168.175.129:8181: connect: connection refused
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:31 +0000 UTC - event for coredns-787d4945fb-pw6s9: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Created: Created container coredns
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:31 +0000 UTC - event for coredns-787d4945fb-pw6s9: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:32 +0000 UTC - event for calico-kube-controllers-657b584867-kw56f: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0"
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:32 +0000 UTC - event for coredns-787d4945fb-pw6s9: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Started: Started container coredns
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:33 +0000 UTC - event for metrics-server-c9574f845-g8gwl: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Created: Created container metrics-server
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:33 +0000 UTC - event for metrics-server-c9574f845-g8gwl: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Started: Started container metrics-server
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:33 +0000 UTC - event for metrics-server-c9574f845-g8gwl: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 5.350482061s (5.35061901s including waiting)
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:38 +0000 UTC - event for calico-kube-controllers-657b584867-kw56f: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 5.345690182s (5.66580592s including waiting)
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:38 +0000 UTC - event for calico-kube-controllers-657b584867-kw56f: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Created: Created container calico-kube-controllers
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:42:38 +0000 UTC - event for calico-kube-controllers-657b584867-kw56f: {kubelet capz-conf-ucrofv-control-plane-rp9w6} Started: Started container calico-kube-controllers
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:44:49 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-8ccjs
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:44:49 +0000 UTC - event for calico-node-windows-8ccjs: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-8ccjs to capz-conf-hh57q
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:44:49 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-7zjxr
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:44:49 +0000 UTC - event for containerd-logger-7zjxr: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-7zjxr to capz-conf-hh57q
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:44:49 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-cbkhg
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:44:49 +0000 UTC - event for kube-proxy-windows-cbkhg: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-cbkhg to capz-conf-hh57q
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:44:51 +0000 UTC - event for calico-node-windows-8ccjs: {kubelet capz-conf-hh57q} FailedMount: MountVolume.SetUp failed for volume "kubeadm-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:44:58 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-drqc6
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:44:58 +0000 UTC - event for calico-node-windows-drqc6: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-drqc6 to capz-conf-lsdpj
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:44:58 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-gjj7w
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:44:58 +0000 UTC - event for containerd-logger-gjj7w: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-gjj7w to capz-conf-lsdpj
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:44:58 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-lkb2w
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:44:58 +0000 UTC - event for kube-proxy-windows-lkb2w: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-lkb2w to capz-conf-lsdpj
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:45:00 +0000 UTC - event for calico-node-windows-drqc6: {kubelet capz-conf-lsdpj} FailedMount: MountVolume.SetUp failed for volume "calico-static-rules" : failed to sync configmap cache: timed out waiting for the condition
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:45:00 +0000 UTC - event for containerd-logger-gjj7w: {kubelet capz-conf-lsdpj} FailedMount: MountVolume.SetUp failed for volume "containerd-logger-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:45:10 +0000 UTC - event for calico-node-windows-8ccjs: {kubelet capz-conf-hh57q} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:45:10 +0000 UTC - event for containerd-logger-7zjxr: {kubelet capz-conf-hh57q} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:45:10 +0000 UTC - event for kube-proxy-windows-cbkhg: {kubelet capz-conf-hh57q} Started: Started container kube-proxy
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:45:10 +0000 UTC - event for kube-proxy-windows-cbkhg: {kubelet capz-conf-hh57q} Created: Created container kube-proxy
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:45:10 +0000 UTC - event for kube-proxy-windows-cbkhg: {kubelet capz-conf-hh57q} Pulled: Container image "sigwindowstools/kube-proxy:v1.27.0-alpha.0.28_3f823c0daa0021-calico-hostprocess" already present on machine
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:45:14 +0000 UTC - event for containerd-logger-7zjxr: {kubelet capz-conf-hh57q} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 3.6309725s (3.6309725s including waiting)
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:45:18 +0000 UTC - event for calico-node-windows-drqc6: {kubelet capz-conf-lsdpj} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 18 05:56:20.816: INFO: At 2022-11-18 05:45:18 +0000 UTC - event for containerd-logger-gjj7w: {kubelet capz-conf-lsdpj} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:18 +0000 UTC - event for kube-proxy-windows-lkb2w: {kubelet capz-conf-lsdpj} Created: Created container kube-proxy
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:18 +0000 UTC - event for kube-proxy-windows-lkb2w: {kubelet capz-conf-lsdpj} Pulled: Container image "sigwindowstools/kube-proxy:v1.27.0-alpha.0.28_3f823c0daa0021-calico-hostprocess" already present on machine
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:18 +0000 UTC - event for kube-proxy-windows-lkb2w: {kubelet capz-conf-lsdpj} Started: Started container kube-proxy
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:19 +0000 UTC - event for calico-node-windows-8ccjs: {kubelet capz-conf-hh57q} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 5.6651348s (9.2711107s including waiting)
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:19 +0000 UTC - event for calico-node-windows-8ccjs: {kubelet capz-conf-hh57q} Created: Created container install-cni
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:20 +0000 UTC - event for calico-node-windows-8ccjs: {kubelet capz-conf-hh57q} Started: Started container install-cni
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:22 +0000 UTC - event for calico-node-windows-drqc6: {kubelet capz-conf-lsdpj} Created: Created container install-cni
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:22 +0000 UTC - event for calico-node-windows-drqc6: {kubelet capz-conf-lsdpj} Started: Started container install-cni
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:22 +0000 UTC - event for calico-node-windows-drqc6: {kubelet capz-conf-lsdpj} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 4.0130638s (4.0130638s including waiting)
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:22 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-nl55w
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:22 +0000 UTC - event for csi-proxy-nl55w: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-nl55w to capz-conf-hh57q
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:23 +0000 UTC - event for containerd-logger-7zjxr: {kubelet capz-conf-hh57q} Created: Created container containerd-logger
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:23 +0000 UTC - event for csi-proxy-nl55w: {kubelet capz-conf-hh57q} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:24 +0000 UTC - event for containerd-logger-7zjxr: {kubelet capz-conf-hh57q} Started: Started container containerd-logger
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:24 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-6gwkw
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:24 +0000 UTC - event for csi-proxy-6gwkw: {kubelet capz-conf-lsdpj} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:24 +0000 UTC - event for csi-proxy-6gwkw: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-6gwkw to capz-conf-lsdpj
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:25 +0000 UTC - event for calico-node-windows-8ccjs: {kubelet capz-conf-hh57q} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:26 +0000 UTC - event for containerd-logger-gjj7w: {kubelet capz-conf-lsdpj} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 4.4618751s (8.4436371s including waiting)
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:27 +0000 UTC - event for calico-node-windows-drqc6: {kubelet capz-conf-lsdpj} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:36 +0000 UTC - event for containerd-logger-gjj7w: {kubelet capz-conf-lsdpj} Started: Started container containerd-logger
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:36 +0000 UTC - event for containerd-logger-gjj7w: {kubelet capz-conf-lsdpj} Created: Created container containerd-logger
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:41 +0000 UTC - event for csi-proxy-nl55w: {kubelet capz-conf-hh57q} Created: Created container csi-proxy
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:41 +0000 UTC - event for csi-proxy-nl55w: {kubelet capz-conf-hh57q} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 17.799861s (17.799861s including waiting)
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:41 +0000 UTC - event for csi-proxy-nl55w: {kubelet capz-conf-hh57q} Started: Started container csi-proxy
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:44 +0000 UTC - event for calico-node-windows-8ccjs: {kubelet capz-conf-hh57q} Started: Started container calico-node-startup
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:44 +0000 UTC - event for calico-node-windows-8ccjs: {kubelet capz-conf-hh57q} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 316.5069ms (316.5069ms including waiting)
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:44 +0000 UTC - event for calico-node-windows-8ccjs: {kubelet capz-conf-hh57q} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:44 +0000 UTC - event for calico-node-windows-8ccjs: {kubelet capz-conf-hh57q} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 3.3142045s (18.6350729s including waiting)
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:44 +0000 UTC - event for calico-node-windows-8ccjs: {kubelet capz-conf-hh57q} Created: Created container calico-node-startup
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:47 +0000 UTC - event for csi-proxy-6gwkw: {kubelet capz-conf-lsdpj} Created: Created container csi-proxy
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:47 +0000 UTC - event for csi-proxy-6gwkw: {kubelet capz-conf-lsdpj} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 21.1577692s (23.0200805s including waiting)
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:48 +0000 UTC - event for csi-proxy-6gwkw: {kubelet capz-conf-lsdpj} Started: Started container csi-proxy
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:51 +0000 UTC - event for calico-node-windows-drqc6: {kubelet capz-conf-lsdpj} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 363.8465ms (363.8465ms including waiting)
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:51 +0000 UTC - event for calico-node-windows-drqc6: {kubelet capz-conf-lsdpj} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:51 +0000 UTC - event for calico-node-windows-drqc6: {kubelet capz-conf-lsdpj} Started: Started container calico-node-startup
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:51 +0000 UTC - event for calico-node-windows-drqc6: {kubelet capz-conf-lsdpj} Created: Created container calico-node-startup
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:51 +0000 UTC - event for calico-node-windows-drqc6: {kubelet capz-conf-lsdpj} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 3.2268868s (23.1545974s including waiting)
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:52 +0000 UTC - event for calico-node-windows-8ccjs: {kubelet capz-conf-hh57q} Created: Created container calico-node-felix
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:52 +0000 UTC - event for calico-node-windows-8ccjs: {kubelet capz-conf-hh57q} Started: Started container calico-node-felix
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:58 +0000 UTC - event for calico-node-windows-drqc6: {kubelet capz-conf-lsdpj} Created: Created container calico-node-felix
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:45:58 +0000 UTC - event for calico-node-windows-drqc6: {kubelet capz-conf-lsdpj} Started: Started container calico-node-felix
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:46:14 +0000 UTC - event for calico-node-windows-8ccjs: {kubelet capz-conf-hh57q} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 330.5134ms (330.5134ms including waiting)
Nov 18 05:56:20.817: INFO: At 2022-11-18 05:46:20 +0000 UTC - event for calico-node-windows-drqc6: {kubelet capz-conf-lsdpj} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 372.7693ms (372.7693ms including waiting)
Nov 18 05:56:20.877: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 18 05:56:20.877: INFO: calico-kube-controllers-657b584867-kw56f capz-conf-ucrofv-control-plane-rp9w6 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:16 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:39 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:39 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:15 +0000 UTC }]
Nov 18 05:56:20.877: INFO: calico-node-99skp capz-conf-ucrofv-control-plane-rp9w6 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:16 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:25 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:25 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:00 +0000 UTC }]
Nov 18 05:56:20.877: INFO: calico-node-windows-8ccjs capz-conf-hh57q Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:25 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:46:22 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:46:22 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:44:49 +0000 UTC }]
Nov 18 05:56:20.878: INFO: calico-node-windows-drqc6 capz-conf-lsdpj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:27 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:46:27 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:46:27 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:44:58 +0000 UTC }]
Nov 18 05:56:20.878: INFO: containerd-logger-7zjxr capz-conf-hh57q Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:44:50 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:24 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:24 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:44:49 +0000 UTC }]
Nov 18 05:56:20.878: INFO: containerd-logger-gjj7w capz-conf-lsdpj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:44:59 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:37 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:37 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:44:58 +0000 UTC }]
Nov 18 05:56:20.878: INFO: coredns-787d4945fb-bm6bb capz-conf-ucrofv-control-plane-rp9w6 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:16 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:30 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:30 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:15 +0000 UTC }]
Nov 18 05:56:20.878: INFO: coredns-787d4945fb-pw6s9 capz-conf-ucrofv-control-plane-rp9w6 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:16 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:32 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:32 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:15 +0000 UTC }]
Nov 18 05:56:20.878: INFO: csi-proxy-6gwkw capz-conf-lsdpj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:24 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:49 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:49 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:24 +0000 UTC }]
Nov 18 05:56:20.878: INFO: csi-proxy-nl55w capz-conf-hh57q Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:22 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:41 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:41 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:22 +0000 UTC }]
Nov 18 05:56:20.878: INFO: etcd-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:41:19 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:41:42 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:41:42 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:41:19 +0000 UTC }]
Nov 18 05:56:20.878: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:20.878: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:20.878: INFO: kube-proxy-886lk capz-conf-ucrofv-control-plane-rp9w6 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:41:40 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:41:45 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:41:45 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:41:40 +0000 UTC }]
Nov 18 05:56:20.878: INFO: kube-proxy-windows-cbkhg capz-conf-hh57q Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:44:50 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:11 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:11 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:44:49 +0000 UTC }]
Nov 18 05:56:20.878: INFO: kube-proxy-windows-lkb2w capz-conf-lsdpj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:44:59 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:18 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:45:18 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:44:58 +0000 UTC }]
Nov 18 05:56:20.878: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
Nov 18 05:56:20.878: INFO: metrics-server-c9574f845-g8gwl capz-conf-ucrofv-control-plane-rp9w6 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:16 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:56 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-18 05:42:15 +0000 UTC }]
Nov 18 05:56:20.878: INFO:
Nov 18 05:56:21.350: INFO:
Logging node info for node capz-conf-hh57q
Nov 18 05:56:21.539: INFO: Node Info: &Node{ObjectMeta:{capz-conf-hh57q 4c517b59-ce05-4a23-b3c2-05bec1247d64 2060 0 2022-11-18 05:44:49 +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:canadacentral failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-hh57q kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-ucrofv cluster.x-k8s.io/cluster-namespace:capz-conf-ucrofv cluster.x-k8s.io/machine:capz-conf-ucrofv-md-win-7759fffb45-fsz2b cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-ucrofv-md-win-7759fffb45 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.73.65 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:b9:e8:22 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet.exe Update v1 2022-11-18 05:44:49 +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":{}}} } {kubeadm Update v1 2022-11-18 05:44:50 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kube-controller-manager Update v1 2022-11-18 05:45:22 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2022-11-18 05:46:11 +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-18 05:46:11 +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-18 05:56:03 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-ucrofv/providers/Microsoft.Compute/virtualMachines/capz-conf-hh57q,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-18 05:56:03 +0000 UTC,LastTransitionTime:2022-11-18 05:44:49 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-18 05:56:03 +0000 UTC,LastTransitionTime:2022-11-18 05:44:49 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-18 05:56:03 +0000 UTC,LastTransitionTime:2022-11-18 05:44:49 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-18 05:56:03 +0000 UTC,LastTransitionTime:2022-11-18 05:45:22 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-hh57q,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-hh57q,SystemUUID:ADB584D3-39D2-4236-86B3-6173CD785891,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.27.0-alpha.0.30+86e8172755f0c3-dirty,KubeProxyVersion:v1.27.0-alpha.0.30+86e8172755f0c3-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.27.0-alpha.0.28_3f823c0daa0021-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 18 05:56:21.539: INFO:
Logging kubelet events for node capz-conf-hh57q
Nov 18 05:56:21.737: INFO:
Logging pods the kubelet thinks is on node capz-conf-hh57q
Nov 18 05:56:21.951: INFO: containerd-logger-7zjxr started at 2022-11-18 05:44:50 +0000 UTC (0+1 container statuses recorded)
Nov 18 05:56:21.951: INFO: Container containerd-logger ready: true, restart count 0
Nov 18 05:56:21.951: INFO: kube-proxy-windows-cbkhg started at 2022-11-18 05:44:50 +0000 UTC (0+1 container statuses recorded)
Nov 18 05:56:21.951: INFO: Container kube-proxy ready: true, restart count 0
Nov 18 05:56:21.951: INFO: calico-node-windows-8ccjs started at 2022-11-18 05:44:50 +0000 UTC (1+2 container statuses recorded)
Nov 18 05:56:21.951: INFO: Init container install-cni ready: true, restart count 0
Nov 18 05:56:21.951: INFO: Container calico-node-felix ready: true, restart count 1
Nov 18 05:56:21.951: INFO: Container calico-node-startup ready: true, restart count 0
Nov 18 05:56:21.951: INFO: csi-proxy-nl55w started at 2022-11-18 05:45:22 +0000 UTC (0+1 container statuses recorded)
Nov 18 05:56:21.951: INFO: Container csi-proxy ready: true, restart count 0
Nov 18 05:56:22.599: INFO:
Latency metrics for node capz-conf-hh57q
Nov 18 05:56:22.599: INFO:
Logging node info for node capz-conf-lsdpj
Nov 18 05:56:22.737: INFO: Node Info: &Node{ObjectMeta:{capz-conf-lsdpj 8efc6985-198f-4f9b-a28e-f2ef7a9e0414 2089 0 2022-11-18 05:44:58 +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:canadacentral failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-lsdpj kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-ucrofv cluster.x-k8s.io/cluster-namespace:capz-conf-ucrofv cluster.x-k8s.io/machine:capz-conf-ucrofv-md-win-7759fffb45-28r5n cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-ucrofv-md-win-7759fffb45 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.93.1 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:6c:b6:3d volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-18 05:44:58 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-18 05:44:58 +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-18 05:45:24 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-18 05:46:13 +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-18 05:46:17 +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-18 05:56:21 +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-ucrofv/providers/Microsoft.Compute/virtualMachines/capz-conf-lsdpj,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-18 05:56:21 +0000 UTC,LastTransitionTime:2022-11-18 05:44:58 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-18 05:56:21 +0000 UTC,LastTransitionTime:2022-11-18 05:44:58 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-18 05:56:21 +0000 UTC,LastTransitionTime:2022-11-18 05:44:58 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-18 05:56:21 +0000 UTC,LastTransitionTime:2022-11-18 05:45:24 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-lsdpj,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-lsdpj,SystemUUID:44A3EF54-17F2-4422-9435-947F4349DA4B,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.27.0-alpha.0.30+86e8172755f0c3-dirty,KubeProxyVersion:v1.27.0-alpha.0.30+86e8172755f0c3-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.27.0-alpha.0.28_3f823c0daa0021-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 18 05:56:22.738: INFO:
Logging kubelet events for node capz-conf-lsdpj
Nov 18 05:56:22.936: INFO:
Logging pods the kubelet thinks is on node capz-conf-lsdpj
Nov 18 05:56:23.150: INFO: csi-proxy-6gwkw started at 2022-11-18 05:45:24 +0000 UTC (0+1 container statuses recorded)
Nov 18 05:56:23.150: INFO: Container csi-proxy ready: true, restart count 0
Nov 18 05:56:23.150: INFO: calico-node-windows-drqc6 started at 2022-11-18 05:44:59 +0000 UTC (1+2 container statuses recorded)
Nov 18 05:56:23.150: INFO: Init container install-cni ready: true, restart count 0
Nov 18 05:56:23.150: INFO: Container calico-node-felix ready: true, restart count 1
Nov 18 05:56:23.150: INFO: Container calico-node-startup ready: true, restart count 0
Nov 18 05:56:23.150: INFO: kube-proxy-windows-lkb2w started at 2022-11-18 05:44:59 +0000 UTC (0+1 container statuses recorded)
Nov 18 05:56:23.150: INFO: Container kube-proxy ready: true, restart count 0
Nov 18 05:56:23.150: INFO: containerd-logger-gjj7w started at 2022-11-18 05:44:59 +0000 UTC (0+1 container statuses recorded)
Nov 18 05:56:23.150: INFO: Container containerd-logger ready: true, restart count 0
Nov 18 05:56:23.810: INFO:
Latency metrics for node capz-conf-lsdpj
Nov 18 05:56:23.810: INFO:
Logging node info for node capz-conf-ucrofv-control-plane-rp9w6
Nov 18 05:56:23.939: INFO: Node Info: &Node{ObjectMeta:{capz-conf-ucrofv-control-plane-rp9w6 5d7d95f5-8264-494c-8c67-f28d58aa9a3f 1822 0 2022-11-18 05:41:34 +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:canadacentral failure-domain.beta.kubernetes.io/zone:canadacentral-1 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-ucrofv-control-plane-rp9w6 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:canadacentral topology.kubernetes.io/zone:canadacentral-1] map[cluster.x-k8s.io/cluster-name:capz-conf-ucrofv cluster.x-k8s.io/cluster-namespace:capz-conf-ucrofv cluster.x-k8s.io/machine:capz-conf-ucrofv-control-plane-65mnl cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-ucrofv-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.175.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2022-11-18 05:41:34 +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-18 05:41:37 +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-18 05:41: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":{}}}} } {kube-controller-manager Update v1 2022-11-18 05:42: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-18 05:42:24 +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-18 05:53:23 +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-ucrofv/providers/Microsoft.Compute/virtualMachines/capz-conf-ucrofv-control-plane-rp9w6,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: {{8344723456 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8239865856 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2022-11-18 05:42:23 +0000 UTC,LastTransitionTime:2022-11-18 05:42:23 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-18 05:53:23 +0000 UTC,LastTransitionTime:2022-11-18 05:41:19 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-18 05:53:23 +0000 UTC,LastTransitionTime:2022-11-18 05:41:19 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-18 05:53:23 +0000 UTC,LastTransitionTime:2022-11-18 05:41:19 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-18 05:53:23 +0000 UTC,LastTransitionTime:2022-11-18 05:42:15 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-ucrofv-control-plane-rp9w6,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:e5ec3c3f94334bd6971e81f9c4953f58,SystemUUID:01eeb8bf-0fc1-e14e-89f9-b9d88730e418,BootID:0774e7fa-fd34-4dc0-a081-2eba1fb3b318,KernelVersion:5.4.0-1091-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.30+86e8172755f0c3,KubeProxyVersion:v1.27.0-alpha.0.30+86e8172755f0c3,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:d21364e0c633a2e2e59c3839983222a0cbd1a20b5f65447dc135d776a3fee704 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.28_3f823c0daa0021],SizeBytes:35317342,},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:4cba827b4565c9d11a9a8648070fa8c3e89f0b9eb88ac1c0a24b5d5a96eda2c1 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.28_3f823c0daa0021],SizeBytes:32243894,},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:74af4dd1f4b40265afc2c24fa21b10d22984f08736e8036c685974aeee2ac2cf gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.28_3f823c0daa0021],SizeBytes:21534369,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:765ffaaf905341722ab5c45eb145623cc74dbf2bfc47f80c05e74d4fd792ae79 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.30_86e8172755f0c3],SizeBytes:21532638,},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:1a77cd3899f75eb90f4ebdb50e81a5a89fbe7984292b185f1168913520813c74 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.28_3f823c0daa0021],SizeBytes:17482420,},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:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},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 18 05:56:23.940: INFO:
Logging kubelet events for node capz-conf-ucrofv-control-plane-rp9w6
Nov 18 05:56:24.137: INFO:
Logging pods the kubelet thinks is on node capz-conf-ucrofv-control-plane-rp9w6
Nov 18 05:56:24.372: INFO: coredns-787d4945fb-pw6s9 started at 2022-11-18 05:42:16 +0000 UTC (0+1 container statuses recorded)
Nov 18 05:56:24.372: INFO: Container coredns ready: true, restart count 0
Nov 18 05:56:24.372: INFO: coredns-787d4945fb-bm6bb started at 2022-11-18 05:42:16 +0000 UTC (0+1 container statuses recorded)
Nov 18 05:56:24.372: INFO: Container coredns ready: true, restart count 0
Nov 18 05:56:24.372: INFO: kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6 started at <nil> (0+0 container statuses recorded)
Nov 18 05:56:24.372: INFO: kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 started at <nil> (0+0 container statuses recorded)
Nov 18 05:56:24.372: INFO: kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 started at <nil> (0+0 container statuses recorded)
Nov 18 05:56:24.372: INFO: kube-proxy-886lk started at 2022-11-18 05:41:40 +0000 UTC (0+1 container statuses recorded)
Nov 18 05:56:24.372: INFO: Container kube-proxy ready: true, restart count 0
Nov 18 05:56:24.372: INFO: etcd-capz-conf-ucrofv-control-plane-rp9w6 started at 2022-11-18 05:41:19 +0000 UTC (0+1 container statuses recorded)
Nov 18 05:56:24.372: INFO: Container etcd ready: true, restart count 0
Nov 18 05:56:24.372: INFO: calico-node-99skp started at 2022-11-18 05:42:00 +0000 UTC (2+1 container statuses recorded)
Nov 18 05:56:24.372: INFO: Init container upgrade-ipam ready: true, restart count 0
Nov 18 05:56:24.372: INFO: Init container install-cni ready: true, restart count 0
Nov 18 05:56:24.372: INFO: Container calico-node ready: true, restart count 0
Nov 18 05:56:24.372: INFO: calico-kube-controllers-657b584867-kw56f started at 2022-11-18 05:42:16 +0000 UTC (0+1 container statuses recorded)
Nov 18 05:56:24.372: INFO: Container calico-kube-controllers ready: true, restart count 0
Nov 18 05:56:24.372: INFO: metrics-server-c9574f845-g8gwl started at 2022-11-18 05:42:16 +0000 UTC (0+1 container statuses recorded)
Nov 18 05:56:24.372: INFO: Container metrics-server ready: true, restart count 0
Nov 18 05:56:24.998: INFO:
Latency metrics for node capz-conf-ucrofv-control-plane-rp9w6
Nov 18 05:56:25.152: INFO: Running kubectl logs on non-ready containers in kube-system
Nov 18 05:56:25.536: INFO: Failed to get logs of pod kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6)
Nov 18 05:56:25.536: INFO: Logs of kube-system/kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6:kube-apiserver on node capz-conf-ucrofv-control-plane-rp9w6
Nov 18 05:56:25.536: INFO: : STARTLOG
ENDLOG for container kube-system:kube-apiserver-capz-conf-ucrofv-control-plane-rp9w6:kube-apiserver
Nov 18 05:56:25.936: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6)
Nov 18 05:56:25.936: INFO: Logs of kube-system/kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6:kube-controller-manager on node capz-conf-ucrofv-control-plane-rp9w6
Nov 18 05:56:25.936: INFO: : STARTLOG
ENDLOG for container kube-system:kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6:kube-controller-manager
Nov 18 05:56:26.336: INFO: Failed to get logs of pod kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6)
Nov 18 05:56:26.336: INFO: Logs of kube-system/kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6:kube-scheduler on node capz-conf-ucrofv-control-plane-rp9w6
Nov 18 05:56:26.336: INFO: : STARTLOG
ENDLOG for container kube-system:kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6:kube-scheduler
Nov 18 05:56:26.336: 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-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
kube-controller-manager-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 Pending []
kube-scheduler-capz-conf-ucrofv-control-plane-rp9w6 capz-conf-ucrofv-control-plane-rp9w6 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({0x66a9bc0?, 0x78952d0?, 0x13?}, {0x75b6e72, 0x4}, {0xc000a3bf20, 0x0, 0x0?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x66a9bc0?, 0x78952d0?, 0x26cd5ed?}, {0xc0000a1f20?, 0x265bb67?, 0xc0000a1f20?})
/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
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
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