PR #111023 pull-kubernetes-e2e-capz-windows-containerd #1591209022386606080
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | pohly: dynamic resource allocation |
| Result | ABORTED |
| Tests | 4 failed / 5 succeeded |
| Started | |
| Elapsed | 1h15m |
| Revision | 7b6e911502a6e0f825986015fc860d075d42b3a2 |
| Refs |
111023 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:249
k8s.io/kubernetes/test/e2e.setupSuite()
test/e2e/e2e.go:249 +0x4de
k8s.io/kubernetes/test/e2e.glob..func1()
test/e2e/e2e.go:81 +0x8f
reflect.Value.call({0x669fa20?, 0x788a1b8?, 0x0?}, {0x75ac416, 0x4}, {0xc0000b9f20, 0x0, 0x0?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x669fa20?, 0x788a1b8?, 0x0?}, {0xc0000b9f20?, 0x0?, 0x0?})
/usr/local/go/src/reflect/value.go:368 +0xbc
[SynchronizedBeforeSuite] TOP-LEVEL
test/e2e/e2e.go:77
Nov 12 00:04:17.855: INFO: >>> kubeConfig: /tmp/kubeconfig
Nov 12 00:04:17.859: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Nov 12 00:04:18.055: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Nov 12 00:04:18.197: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:18.197: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:18.197: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:18.197: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Nov 12 00:04:18.197: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:18.197: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:18.197: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:18.197: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:18.197: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:18.197: INFO:
Nov 12 00:04:20.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:20.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:20.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:20.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Nov 12 00:04:20.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:20.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:20.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:20.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:20.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:20.330: INFO:
Nov 12 00:04:22.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:22.332: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:22.332: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:22.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Nov 12 00:04:22.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:22.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:22.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:22.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:22.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:22.332: INFO:
Nov 12 00:04:24.333: INFO: The status of Pod calico-node-windows-tqsl4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:24.333: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:24.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:24.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:24.333: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Nov 12 00:04:24.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:24.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:24.333: INFO: calico-node-windows-tqsl4 capz-conf-cm7pj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:38 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:04:22 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:04:22 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:05 +0000 UTC }]
Nov 12 00:04:24.333: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:24.333: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:24.333: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:24.333: INFO:
Nov 12 00:04:26.337: INFO: The status of Pod calico-node-windows-tqsl4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:26.337: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:26.337: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:26.337: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:26.337: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Nov 12 00:04:26.337: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:26.337: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:26.337: INFO: calico-node-windows-tqsl4 capz-conf-cm7pj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:38 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:04:22 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:04:22 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:05 +0000 UTC }]
Nov 12 00:04:26.337: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:26.337: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:26.337: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:26.337: INFO:
Nov 12 00:04:28.335: INFO: The status of Pod calico-node-windows-tqsl4 is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:28.335: INFO: The status of Pod calico-node-windows-wtrbt is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:28.335: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:28.335: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:28.335: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:28.335: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Nov 12 00:04:28.335: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:28.335: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:28.335: INFO: calico-node-windows-tqsl4 capz-conf-cm7pj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:38 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:04:22 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:04:22 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:05 +0000 UTC }]
Nov 12 00:04:28.335: INFO: calico-node-windows-wtrbt capz-conf-ld5bg Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:39 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:04:27 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:04:27 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:10 +0000 UTC }]
Nov 12 00:04:28.335: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:28.335: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:28.335: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:28.335: INFO:
Nov 12 00:04:30.335: INFO: The status of Pod calico-node-windows-wtrbt is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:30.335: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:30.335: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:30.335: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:30.335: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Nov 12 00:04:30.335: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:30.335: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:30.335: INFO: calico-node-windows-wtrbt capz-conf-ld5bg Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:39 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:04:27 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:04:27 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:10 +0000 UTC }]
Nov 12 00:04:30.335: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:30.335: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:30.335: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:30.335: INFO:
Nov 12 00:04:32.333: INFO: The status of Pod calico-node-windows-wtrbt is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:32.333: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:32.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:32.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:32.333: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Nov 12 00:04:32.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:32.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:32.333: INFO: calico-node-windows-wtrbt capz-conf-ld5bg Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:39 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:04:27 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:04:27 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:10 +0000 UTC }]
Nov 12 00:04:32.333: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:32.333: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:32.333: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:32.333: INFO:
Nov 12 00:04:34.333: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:34.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:34.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:34.333: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Nov 12 00:04:34.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:34.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:34.333: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:34.333: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:34.333: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:34.333: INFO:
Nov 12 00:04:36.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:36.332: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:36.332: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:36.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Nov 12 00:04:36.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:36.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:36.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:36.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:36.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:36.332: INFO:
Nov 12 00:04:38.333: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:38.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:38.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:38.333: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Nov 12 00:04:38.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:38.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:38.333: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:38.333: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:38.333: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:38.333: INFO:
Nov 12 00:04:40.335: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:40.335: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:40.335: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:40.335: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Nov 12 00:04:40.335: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:40.335: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:40.335: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:40.335: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:40.335: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:40.335: INFO:
Nov 12 00:04:42.337: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:42.337: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:42.337: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:42.337: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Nov 12 00:04:42.337: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:42.337: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:42.337: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:42.337: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:42.337: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:42.337: INFO:
Nov 12 00:04:44.331: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:44.331: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:44.331: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:44.331: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Nov 12 00:04:44.331: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:44.331: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:44.331: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:44.331: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:44.331: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:44.331: INFO:
Nov 12 00:04:46.339: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:46.339: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:46.339: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:46.339: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Nov 12 00:04:46.339: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:46.339: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:46.339: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:46.339: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:46.339: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:46.339: INFO:
Nov 12 00:04:48.340: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:48.340: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:48.340: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:48.340: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
Nov 12 00:04:48.340: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:48.340: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:48.340: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:48.340: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:48.340: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:48.340: INFO:
Nov 12 00:04:50.354: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:50.354: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:50.354: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:50.354: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
Nov 12 00:04:50.354: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:50.354: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:50.354: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:50.354: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:50.354: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:50.354: INFO:
Nov 12 00:04:52.340: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:52.340: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:52.340: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:52.340: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
Nov 12 00:04:52.340: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:52.340: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:52.340: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:52.340: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:52.340: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:52.340: INFO:
Nov 12 00:04:54.333: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:54.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:54.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:54.333: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
Nov 12 00:04:54.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:54.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:54.333: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:54.333: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:54.333: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:54.333: INFO:
Nov 12 00:04:56.340: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:56.340: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:56.340: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:56.340: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
Nov 12 00:04:56.340: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:56.340: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:56.341: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:56.341: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:56.341: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:56.341: INFO:
Nov 12 00:04:58.341: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:58.341: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:58.341: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:04:58.341: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
Nov 12 00:04:58.341: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:04:58.341: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:04:58.341: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:58.341: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:58.341: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:04:58.341: INFO:
Nov 12 00:05:00.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:00.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:00.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:00.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
Nov 12 00:05:00.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:00.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:00.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:00.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:00.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:00.330: INFO:
Nov 12 00:05:02.337: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:02.337: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:02.337: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:02.337: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
Nov 12 00:05:02.337: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:02.337: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:02.337: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:02.337: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:02.337: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:02.337: INFO:
Nov 12 00:05:04.333: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:04.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:04.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:04.333: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
Nov 12 00:05:04.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:04.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:04.333: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:04.333: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:04.333: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:04.333: INFO:
Nov 12 00:05:06.336: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:06.336: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:06.336: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:06.336: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
Nov 12 00:05:06.336: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:06.336: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:06.336: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:06.336: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:06.336: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:06.336: INFO:
Nov 12 00:05:08.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:08.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:08.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:08.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
Nov 12 00:05:08.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:08.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:08.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:08.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:08.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:08.330: INFO:
Nov 12 00:05:10.334: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:10.334: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:10.334: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:10.334: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
Nov 12 00:05:10.334: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:10.334: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:10.334: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:10.334: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:10.334: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:10.334: INFO:
Nov 12 00:05:12.341: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:12.341: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:12.341: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:12.341: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
Nov 12 00:05:12.341: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:12.341: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:12.341: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:12.341: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:12.341: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:12.341: INFO:
Nov 12 00:05:14.338: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:14.338: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:14.338: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:14.338: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
Nov 12 00:05:14.338: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:14.338: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:14.338: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:14.338: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:14.338: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:14.338: INFO:
Nov 12 00:05:16.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:16.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:16.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:16.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
Nov 12 00:05:16.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:16.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:16.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:16.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:16.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:16.330: INFO:
Nov 12 00:05:18.336: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:18.336: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:18.336: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:18.336: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
Nov 12 00:05:18.336: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:18.336: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:18.336: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:18.336: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:18.336: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:18.336: INFO:
Nov 12 00:05:20.342: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:20.342: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:20.342: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:20.342: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
Nov 12 00:05:20.342: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:20.342: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:20.342: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:20.342: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:20.342: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:20.342: INFO:
Nov 12 00:05:22.338: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:22.338: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:22.338: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:22.338: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
Nov 12 00:05:22.338: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:22.338: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:22.338: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:22.338: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:22.338: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:22.338: INFO:
Nov 12 00:05:24.335: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:24.335: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:24.335: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:24.335: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
Nov 12 00:05:24.335: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:24.335: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:24.335: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:24.335: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:24.335: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:24.335: INFO:
Nov 12 00:05:26.333: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:26.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:26.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:26.333: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
Nov 12 00:05:26.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:26.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:26.333: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:26.333: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:26.333: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:26.333: INFO:
Nov 12 00:05:28.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:28.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:28.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:28.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
Nov 12 00:05:28.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:28.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:28.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:28.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:28.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:28.330: INFO:
Nov 12 00:05:30.336: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:30.336: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:30.336: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:30.336: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
Nov 12 00:05:30.336: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:30.336: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:30.336: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:30.336: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:30.336: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:30.336: INFO:
Nov 12 00:05:32.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:32.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:32.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:32.333: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
Nov 12 00:05:32.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:32.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:32.333: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:32.333: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:32.333: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:32.333: INFO:
Nov 12 00:05:34.339: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:34.339: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:34.339: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:34.339: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
Nov 12 00:05:34.339: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:34.339: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:34.339: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:34.339: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:34.339: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:34.339: INFO:
Nov 12 00:05:36.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:36.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:36.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:36.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
Nov 12 00:05:36.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:36.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:36.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:36.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:36.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:36.327: INFO:
Nov 12 00:05:38.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:38.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:38.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:38.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
Nov 12 00:05:38.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:38.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:38.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:38.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:38.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:38.328: INFO:
Nov 12 00:05:40.334: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:40.334: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:40.334: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:40.334: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
Nov 12 00:05:40.334: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:40.334: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:40.334: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:40.334: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:40.334: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:40.334: INFO:
Nov 12 00:05:42.338: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:42.338: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:42.338: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:42.338: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
Nov 12 00:05:42.338: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:42.338: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:42.338: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:42.338: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:42.338: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:42.338: INFO:
Nov 12 00:05:44.340: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:44.340: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:44.340: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:44.340: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
Nov 12 00:05:44.340: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:44.340: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:44.340: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:44.340: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:44.340: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:44.340: INFO:
Nov 12 00:05:46.340: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:46.340: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:46.340: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:46.341: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
Nov 12 00:05:46.341: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:46.341: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:46.341: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:46.341: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:46.341: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:46.341: INFO:
Nov 12 00:05:48.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:48.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:48.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:48.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
Nov 12 00:05:48.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:48.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:48.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:48.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:48.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:48.330: INFO:
Nov 12 00:05:50.333: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:50.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:50.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:50.333: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
Nov 12 00:05:50.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:50.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:50.333: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:50.333: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:50.333: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:50.333: INFO:
Nov 12 00:05:52.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:52.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:52.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:52.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
Nov 12 00:05:52.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:52.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:52.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:52.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:52.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:52.330: INFO:
Nov 12 00:05:54.445: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:54.445: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:54.445: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:54.445: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
Nov 12 00:05:54.445: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:54.445: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:54.445: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:54.445: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:54.445: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:54.445: INFO:
Nov 12 00:05:56.364: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:56.364: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:56.364: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:56.364: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
Nov 12 00:05:56.364: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:56.364: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:56.364: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:56.364: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:56.364: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:56.364: INFO:
Nov 12 00:05:58.337: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:58.337: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:58.337: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:05:58.337: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
Nov 12 00:05:58.337: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:05:58.337: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:05:58.337: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:58.337: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:58.337: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:05:58.337: INFO:
Nov 12 00:06:00.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:00.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:00.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:00.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
Nov 12 00:06:00.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:00.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:00.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:00.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:00.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:00.329: INFO:
Nov 12 00:06:02.334: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:02.334: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:02.334: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:02.334: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
Nov 12 00:06:02.334: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:02.334: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:02.334: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:02.334: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:02.334: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:02.334: INFO:
Nov 12 00:06:04.331: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:04.331: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:04.331: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:04.331: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
Nov 12 00:06:04.331: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:04.331: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:04.331: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:04.331: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:04.331: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:04.331: INFO:
Nov 12 00:06:06.333: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:06.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:06.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:06.333: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
Nov 12 00:06:06.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:06.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:06.333: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:06.333: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:06.333: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:06.333: INFO:
Nov 12 00:06:08.337: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:08.337: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:08.337: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:08.337: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
Nov 12 00:06:08.337: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:08.337: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:08.337: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:08.337: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:08.337: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:08.337: INFO:
Nov 12 00:06:10.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:10.332: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:10.332: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:10.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
Nov 12 00:06:10.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:10.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:10.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:10.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:10.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:10.332: INFO:
Nov 12 00:06:12.339: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:12.339: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:12.339: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:12.339: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
Nov 12 00:06:12.339: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:12.339: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:12.339: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:12.339: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:12.339: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:12.339: INFO:
Nov 12 00:06:14.336: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:14.336: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:14.336: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:14.337: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
Nov 12 00:06:14.337: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:14.337: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:14.337: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:14.337: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:14.337: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:14.337: INFO:
Nov 12 00:06:16.333: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:16.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:16.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:16.333: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
Nov 12 00:06:16.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:16.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:16.333: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:16.333: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:16.333: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:16.333: INFO:
Nov 12 00:06:18.335: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:18.335: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:18.335: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:18.335: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
Nov 12 00:06:18.335: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:18.335: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:18.335: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:18.335: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:18.335: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:18.335: INFO:
Nov 12 00:06:20.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:20.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:20.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:20.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
Nov 12 00:06:20.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:20.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:20.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:20.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:20.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:20.329: INFO:
Nov 12 00:06:22.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:22.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:22.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:22.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
Nov 12 00:06:22.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:22.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:22.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:22.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:22.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:22.330: INFO:
Nov 12 00:06:24.334: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:24.334: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:24.334: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:24.334: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
Nov 12 00:06:24.334: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:24.334: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:24.334: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:24.334: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:24.334: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:24.334: INFO:
Nov 12 00:06:26.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:26.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:26.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:26.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
Nov 12 00:06:26.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:26.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:26.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:26.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:26.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:26.330: INFO:
Nov 12 00:06:28.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:28.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:28.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:28.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
Nov 12 00:06:28.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:28.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:28.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:28.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:28.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:28.328: INFO:
Nov 12 00:06:30.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:30.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:30.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:30.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
Nov 12 00:06:30.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:30.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:30.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:30.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:30.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:30.330: INFO:
Nov 12 00:06:32.334: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:32.334: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:32.334: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:32.334: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
Nov 12 00:06:32.334: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:32.334: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:32.334: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:32.334: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:32.334: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:32.334: INFO:
Nov 12 00:06:34.345: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:34.345: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:34.345: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:34.345: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
Nov 12 00:06:34.345: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:34.345: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:34.345: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:34.345: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:34.345: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:34.345: INFO:
Nov 12 00:06:36.336: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:36.336: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:36.336: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:36.336: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
Nov 12 00:06:36.336: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:36.336: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:36.336: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:36.336: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:36.336: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:36.336: INFO:
Nov 12 00:06:38.334: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:38.334: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:38.334: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:38.334: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
Nov 12 00:06:38.334: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:38.334: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:38.334: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:38.334: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:38.334: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:38.334: INFO:
Nov 12 00:06:40.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:40.332: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:40.332: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:40.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
Nov 12 00:06:40.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:40.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:40.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:40.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:40.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:40.332: INFO:
Nov 12 00:06:42.334: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:42.334: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:42.334: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:42.334: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
Nov 12 00:06:42.334: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:42.334: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:42.334: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:42.334: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:42.334: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:42.334: INFO:
Nov 12 00:06:44.336: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:44.336: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:44.336: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:44.336: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
Nov 12 00:06:44.336: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:44.336: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:44.336: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:44.336: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:44.336: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:44.336: INFO:
Nov 12 00:06:46.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:46.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:46.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:46.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
Nov 12 00:06:46.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:46.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:46.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:46.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:46.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:46.329: INFO:
Nov 12 00:06:48.336: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:48.336: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:48.336: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:48.336: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
Nov 12 00:06:48.336: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:48.336: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:48.336: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:48.336: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:48.336: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:48.336: INFO:
Nov 12 00:06:50.333: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:50.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:50.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:50.333: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
Nov 12 00:06:50.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:50.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:50.333: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:50.333: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:50.333: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:50.333: INFO:
Nov 12 00:06:52.348: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:52.348: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:52.348: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:52.348: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
Nov 12 00:06:52.348: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:52.348: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:52.348: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:52.348: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:52.348: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:52.348: INFO:
Nov 12 00:06:54.339: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:54.339: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:54.339: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:54.339: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
Nov 12 00:06:54.339: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:54.339: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:54.339: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:54.339: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:54.340: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:54.340: INFO:
Nov 12 00:06:56.334: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:56.334: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:56.334: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:56.334: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
Nov 12 00:06:56.334: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:56.334: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:56.334: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:56.334: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:56.334: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:56.334: INFO:
Nov 12 00:06:58.331: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:58.331: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:58.331: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:06:58.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
Nov 12 00:06:58.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:06:58.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:06:58.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:58.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:58.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:06:58.332: INFO:
Nov 12 00:07:00.333: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:00.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:00.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:00.333: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
Nov 12 00:07:00.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:00.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:00.333: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:00.333: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:00.333: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:00.333: INFO:
Nov 12 00:07:02.339: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:02.339: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:02.339: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:02.339: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
Nov 12 00:07:02.339: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:02.339: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:02.339: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:02.339: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:02.339: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:02.339: INFO:
Nov 12 00:07:04.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:04.332: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:04.332: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:04.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
Nov 12 00:07:04.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:04.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:04.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:04.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:04.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:04.332: INFO:
Nov 12 00:07:06.331: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:06.331: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:06.331: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:06.331: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
Nov 12 00:07:06.331: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:06.331: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:06.331: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:06.331: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:06.331: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:06.331: INFO:
Nov 12 00:07:08.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:08.332: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:08.332: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:08.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
Nov 12 00:07:08.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:08.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:08.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:08.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:08.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:08.332: INFO:
Nov 12 00:07:10.442: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:10.442: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:10.442: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:10.442: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
Nov 12 00:07:10.442: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:10.442: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:10.442: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:10.442: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:10.442: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:10.442: INFO:
Nov 12 00:07:12.331: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:12.331: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:12.331: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:12.331: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
Nov 12 00:07:12.331: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:12.331: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:12.331: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:12.331: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:12.331: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:12.331: INFO:
Nov 12 00:07:14.339: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:14.339: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:14.339: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:14.339: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
Nov 12 00:07:14.339: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:14.339: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:14.339: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:14.339: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:14.339: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:14.339: INFO:
Nov 12 00:07:16.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:16.331: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:16.331: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:16.331: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
Nov 12 00:07:16.331: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:16.331: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:16.331: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:16.331: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:16.331: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:16.331: INFO:
Nov 12 00:07:18.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:18.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:18.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:18.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
Nov 12 00:07:18.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:18.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:18.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:18.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:18.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:18.330: INFO:
Nov 12 00:07:20.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:20.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:20.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:20.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
Nov 12 00:07:20.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:20.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:20.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:20.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:20.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:20.329: INFO:
Nov 12 00:07:22.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:22.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:22.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:22.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
Nov 12 00:07:22.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:22.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:22.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:22.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:22.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:22.328: INFO:
Nov 12 00:07:24.341: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:24.341: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:24.341: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:24.341: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
Nov 12 00:07:24.341: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:24.341: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:24.341: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:24.341: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:24.341: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:24.341: INFO:
Nov 12 00:07:26.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:26.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:26.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:26.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
Nov 12 00:07:26.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:26.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:26.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:26.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:26.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:26.327: INFO:
Nov 12 00:07:28.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:28.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:28.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:28.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
Nov 12 00:07:28.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:28.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:28.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:28.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:28.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:28.328: INFO:
Nov 12 00:07:30.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:30.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:30.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:30.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
Nov 12 00:07:30.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:30.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:30.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:30.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:30.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:30.328: INFO:
Nov 12 00:07:32.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:32.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:32.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:32.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
Nov 12 00:07:32.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:32.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:32.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:32.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:32.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:32.328: INFO:
Nov 12 00:07:34.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:34.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:34.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:34.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
Nov 12 00:07:34.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:34.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:34.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:34.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:34.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:34.327: INFO:
Nov 12 00:07:36.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:36.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:36.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:36.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
Nov 12 00:07:36.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:36.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:36.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:36.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:36.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:36.328: INFO:
Nov 12 00:07:38.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:38.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:38.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:38.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
Nov 12 00:07:38.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:38.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:38.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:38.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:38.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:38.327: INFO:
Nov 12 00:07:40.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:40.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:40.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:40.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
Nov 12 00:07:40.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:40.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:40.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:40.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:40.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:40.328: INFO:
Nov 12 00:07:42.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:42.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:42.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:42.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
Nov 12 00:07:42.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:42.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:42.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:42.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:42.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:42.327: INFO:
Nov 12 00:07:44.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:44.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:44.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:44.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
Nov 12 00:07:44.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:44.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:44.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:44.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:44.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:44.328: INFO:
Nov 12 00:07:46.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:46.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:46.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:46.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
Nov 12 00:07:46.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:46.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:46.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:46.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:46.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:46.327: INFO:
Nov 12 00:07:48.331: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:48.331: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:48.331: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:48.331: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
Nov 12 00:07:48.331: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:48.331: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:48.331: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:48.331: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:48.331: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:48.331: INFO:
Nov 12 00:07:50.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:50.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:50.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:50.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
Nov 12 00:07:50.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:50.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:50.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:50.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:50.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:50.330: INFO:
Nov 12 00:07:52.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:52.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:52.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:52.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
Nov 12 00:07:52.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:52.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:52.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:52.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:52.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:52.327: INFO:
Nov 12 00:07:54.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:54.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:54.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:54.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
Nov 12 00:07:54.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:54.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:54.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:54.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:54.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:54.328: INFO:
Nov 12 00:07:56.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:56.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:56.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:56.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
Nov 12 00:07:56.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:56.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:56.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:56.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:56.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:56.327: INFO:
Nov 12 00:07:58.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:58.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:58.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:07:58.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
Nov 12 00:07:58.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:07:58.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:07:58.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:58.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:58.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:07:58.330: INFO:
Nov 12 00:08:00.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:00.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:00.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:00.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
Nov 12 00:08:00.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:00.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:00.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:00.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:00.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:00.327: INFO:
Nov 12 00:08:02.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:02.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:02.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:02.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
Nov 12 00:08:02.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:02.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:02.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:02.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:02.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:02.330: INFO:
Nov 12 00:08:04.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:04.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:04.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:04.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
Nov 12 00:08:04.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:04.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:04.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:04.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:04.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:04.328: INFO:
Nov 12 00:08:06.326: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:06.326: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:06.326: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:06.326: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
Nov 12 00:08:06.326: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:06.326: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:06.326: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:06.326: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:06.326: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:06.326: INFO:
Nov 12 00:08:08.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:08.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:08.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:08.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
Nov 12 00:08:08.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:08.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:08.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:08.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:08.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:08.328: INFO:
Nov 12 00:08:10.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:10.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:10.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:10.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
Nov 12 00:08:10.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:10.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:10.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:10.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:10.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:10.327: INFO:
Nov 12 00:08:12.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:12.331: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:12.331: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:12.331: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
Nov 12 00:08:12.331: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:12.331: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:12.331: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:12.331: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:12.331: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:12.331: INFO:
Nov 12 00:08:14.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:14.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:14.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:14.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
Nov 12 00:08:14.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:14.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:14.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:14.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:14.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:14.328: INFO:
Nov 12 00:08:16.333: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:16.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:16.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:16.333: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
Nov 12 00:08:16.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:16.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:16.334: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:16.334: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:16.334: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:16.334: INFO:
Nov 12 00:08:18.331: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:18.331: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:18.331: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:18.331: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
Nov 12 00:08:18.331: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:18.331: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:18.331: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:18.331: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:18.331: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:18.331: INFO:
Nov 12 00:08:20.326: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:20.326: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:20.326: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:20.326: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
Nov 12 00:08:20.326: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:20.326: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:20.326: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:20.326: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:20.326: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:20.326: INFO:
Nov 12 00:08:22.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:22.332: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:22.332: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:22.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
Nov 12 00:08:22.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:22.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:22.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:22.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:22.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:22.332: INFO:
Nov 12 00:08:24.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:24.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:24.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:24.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
Nov 12 00:08:24.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:24.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:24.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:24.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:24.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:24.330: INFO:
Nov 12 00:08:26.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:26.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:26.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:26.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
Nov 12 00:08:26.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:26.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:26.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:26.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:26.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:26.329: INFO:
Nov 12 00:08:28.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:28.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:28.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:28.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
Nov 12 00:08:28.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:28.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:28.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:28.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:28.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:28.329: INFO:
Nov 12 00:08:30.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:30.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:30.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:30.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
Nov 12 00:08:30.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:30.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:30.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:30.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:30.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:30.329: INFO:
Nov 12 00:08:32.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:32.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:32.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:32.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
Nov 12 00:08:32.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:32.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:32.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:32.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:32.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:32.329: INFO:
Nov 12 00:08:34.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:34.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:34.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:34.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
Nov 12 00:08:34.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:34.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:34.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:34.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:34.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:34.327: INFO:
Nov 12 00:08:36.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:36.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:36.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:36.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
Nov 12 00:08:36.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:36.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:36.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:36.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:36.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:36.327: INFO:
Nov 12 00:08:38.333: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:38.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:38.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:38.333: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
Nov 12 00:08:38.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:38.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:38.333: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:38.333: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:38.333: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:38.333: INFO:
Nov 12 00:08:40.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:40.332: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:40.332: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:40.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
Nov 12 00:08:40.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:40.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:40.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:40.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:40.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:40.332: INFO:
Nov 12 00:08:42.333: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:42.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:42.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:42.333: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
Nov 12 00:08:42.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:42.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:42.333: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:42.333: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:42.333: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:42.333: INFO:
Nov 12 00:08:44.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:44.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:44.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:44.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
Nov 12 00:08:44.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:44.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:44.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:44.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:44.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:44.328: INFO:
Nov 12 00:08:46.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:46.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:46.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:46.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
Nov 12 00:08:46.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:46.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:46.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:46.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:46.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:46.328: INFO:
Nov 12 00:08:48.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:48.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:48.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:48.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
Nov 12 00:08:48.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:48.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:48.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:48.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:48.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:48.327: INFO:
Nov 12 00:08:50.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:50.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:50.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:50.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
Nov 12 00:08:50.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:50.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:50.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:50.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:50.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:50.328: INFO:
Nov 12 00:08:52.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:52.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:52.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:52.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
Nov 12 00:08:52.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:52.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:52.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:52.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:52.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:52.327: INFO:
Nov 12 00:08:54.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:54.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:54.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:54.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
Nov 12 00:08:54.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:54.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:54.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:54.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:54.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:54.329: INFO:
Nov 12 00:08:56.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:56.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:56.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:56.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
Nov 12 00:08:56.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:56.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:56.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:56.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:56.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:56.328: INFO:
Nov 12 00:08:58.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:58.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:58.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:08:58.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
Nov 12 00:08:58.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:08:58.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:08:58.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:58.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:58.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:08:58.328: INFO:
Nov 12 00:09:00.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:00.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:00.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:00.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
Nov 12 00:09:00.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:00.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:00.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:00.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:00.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:00.327: INFO:
Nov 12 00:09:02.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:02.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:02.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:02.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
Nov 12 00:09:02.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:02.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:02.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:02.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:02.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:02.330: INFO:
Nov 12 00:09:04.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:04.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:04.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:04.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
Nov 12 00:09:04.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:04.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:04.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:04.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:04.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:04.327: INFO:
Nov 12 00:09:06.326: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:06.326: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:06.326: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:06.326: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
Nov 12 00:09:06.326: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:06.326: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:06.326: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:06.326: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:06.326: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:06.326: INFO:
Nov 12 00:09:08.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:08.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:08.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:08.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
Nov 12 00:09:08.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:08.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:08.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:08.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:08.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:08.330: INFO:
Nov 12 00:09:10.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:10.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:10.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:10.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
Nov 12 00:09:10.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:10.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:10.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:10.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:10.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:10.328: INFO:
Nov 12 00:09:12.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:12.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:12.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:12.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
Nov 12 00:09:12.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:12.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:12.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:12.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:12.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:12.327: INFO:
Nov 12 00:09:14.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:14.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:14.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:14.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
Nov 12 00:09:14.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:14.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:14.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:14.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:14.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:14.328: INFO:
Nov 12 00:09:16.326: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:16.326: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:16.326: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:16.326: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
Nov 12 00:09:16.326: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:16.326: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:16.326: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:16.326: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:16.326: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:16.326: INFO:
Nov 12 00:09:18.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:18.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:18.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:18.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
Nov 12 00:09:18.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:18.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:18.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:18.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:18.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:18.327: INFO:
Nov 12 00:09:20.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:20.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:20.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:20.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
Nov 12 00:09:20.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:20.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:20.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:20.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:20.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:20.327: INFO:
Nov 12 00:09:22.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:22.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:22.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:22.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
Nov 12 00:09:22.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:22.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:22.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:22.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:22.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:22.329: INFO:
Nov 12 00:09:24.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:24.332: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:24.332: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:24.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
Nov 12 00:09:24.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:24.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:24.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:24.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:24.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:24.332: INFO:
Nov 12 00:09:26.326: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:26.326: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:26.326: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:26.326: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
Nov 12 00:09:26.326: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:26.326: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:26.326: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:26.326: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:26.326: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:26.326: INFO:
Nov 12 00:09:28.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:28.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:28.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:28.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
Nov 12 00:09:28.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:28.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:28.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:28.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:28.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:28.328: INFO:
Nov 12 00:09:30.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:30.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:30.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:30.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
Nov 12 00:09:30.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:30.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:30.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:30.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:30.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:30.327: INFO:
Nov 12 00:09:32.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:32.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:32.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:32.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
Nov 12 00:09:32.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:32.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:32.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:32.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:32.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:32.329: INFO:
Nov 12 00:09:34.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:34.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:34.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:34.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
Nov 12 00:09:34.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:34.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:34.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:34.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:34.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:34.330: INFO:
Nov 12 00:09:36.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:36.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:36.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:36.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
Nov 12 00:09:36.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:36.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:36.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:36.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:36.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:36.328: INFO:
Nov 12 00:09:38.346: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:38.346: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:38.346: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:38.346: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
Nov 12 00:09:38.346: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:38.346: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:38.346: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:38.346: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:38.346: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:38.346: INFO:
Nov 12 00:09:40.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:40.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:40.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:40.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
Nov 12 00:09:40.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:40.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:40.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:40.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:40.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:40.330: INFO:
Nov 12 00:09:42.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:42.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:42.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:42.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
Nov 12 00:09:42.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:42.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:42.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:42.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:42.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:42.329: INFO:
Nov 12 00:09:44.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:44.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:44.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:44.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
Nov 12 00:09:44.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:44.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:44.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:44.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:44.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:44.329: INFO:
Nov 12 00:09:46.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:46.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:46.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:46.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
Nov 12 00:09:46.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:46.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:46.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:46.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:46.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:46.327: INFO:
Nov 12 00:09:48.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:48.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:48.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:48.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
Nov 12 00:09:48.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:48.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:48.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:48.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:48.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:48.329: INFO:
Nov 12 00:09:50.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:50.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:50.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:50.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
Nov 12 00:09:50.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:50.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:50.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:50.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:50.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:50.327: INFO:
Nov 12 00:09:52.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:52.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:52.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:52.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
Nov 12 00:09:52.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:52.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:52.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:52.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:52.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:52.327: INFO:
Nov 12 00:09:54.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:54.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:54.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:54.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
Nov 12 00:09:54.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:54.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:54.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:54.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:54.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:54.328: INFO:
Nov 12 00:09:56.339: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:56.339: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:56.339: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:56.339: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
Nov 12 00:09:56.339: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:56.339: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:56.339: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:56.339: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:56.339: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:56.339: INFO:
Nov 12 00:09:58.343: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:58.343: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:58.343: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:09:58.343: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
Nov 12 00:09:58.343: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:09:58.343: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:09:58.343: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:58.343: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:58.343: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:09:58.343: INFO:
Nov 12 00:10:00.345: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:00.345: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:00.345: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:00.345: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
Nov 12 00:10:00.345: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:00.345: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:00.345: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:00.345: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:00.345: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:00.345: INFO:
Nov 12 00:10:02.345: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:02.345: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:02.345: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:02.345: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
Nov 12 00:10:02.345: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:02.345: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:02.345: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:02.345: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:02.345: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:02.345: INFO:
Nov 12 00:10:04.341: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:04.341: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:04.341: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:04.341: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
Nov 12 00:10:04.341: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:04.341: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:04.341: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:04.341: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:04.341: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:04.341: INFO:
Nov 12 00:10:06.340: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:06.340: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:06.340: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:06.340: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
Nov 12 00:10:06.340: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:06.340: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:06.340: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:06.340: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:06.340: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:06.340: INFO:
Nov 12 00:10:08.339: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:08.339: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:08.339: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:08.339: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
Nov 12 00:10:08.339: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:08.339: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:08.339: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:08.339: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:08.339: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:08.339: INFO:
Nov 12 00:10:10.339: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:10.339: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:10.339: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:10.339: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
Nov 12 00:10:10.339: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:10.339: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:10.339: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:10.339: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:10.339: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:10.339: INFO:
Nov 12 00:10:12.343: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:12.343: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:12.343: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:12.343: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
Nov 12 00:10:12.343: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:12.344: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:12.344: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:12.344: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:12.344: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:12.344: INFO:
Nov 12 00:10:14.340: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:14.340: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:14.340: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:14.340: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
Nov 12 00:10:14.340: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:14.340: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:14.340: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:14.340: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:14.340: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:14.340: INFO:
Nov 12 00:10:16.342: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:16.342: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:16.342: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:16.342: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
Nov 12 00:10:16.342: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:16.342: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:16.342: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:16.342: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:16.342: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:16.342: INFO:
Nov 12 00:10:18.339: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:18.339: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:18.339: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:18.339: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
Nov 12 00:10:18.339: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:18.339: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:18.339: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:18.339: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:18.339: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:18.339: INFO:
Nov 12 00:10:20.341: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:20.341: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:20.341: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:20.341: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
Nov 12 00:10:20.341: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:20.341: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:20.341: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:20.341: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:20.341: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:20.341: INFO:
Nov 12 00:10:22.342: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:22.342: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:22.342: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:22.342: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
Nov 12 00:10:22.342: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:22.342: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:22.342: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:22.342: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:22.342: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:22.342: INFO:
Nov 12 00:10:24.340: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:24.340: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:24.340: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:24.340: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
Nov 12 00:10:24.340: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:24.340: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:24.340: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:24.340: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:24.340: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:24.340: INFO:
Nov 12 00:10:26.345: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:26.345: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:26.345: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:26.345: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
Nov 12 00:10:26.345: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:26.345: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:26.345: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:26.345: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:26.345: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:26.345: INFO:
Nov 12 00:10:28.340: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:28.340: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:28.340: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:28.340: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
Nov 12 00:10:28.340: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:28.340: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:28.340: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:28.340: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:28.340: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:28.340: INFO:
Nov 12 00:10:30.339: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:30.339: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:30.339: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:30.339: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
Nov 12 00:10:30.339: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:30.339: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:30.339: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:30.339: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:30.339: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:30.339: INFO:
Nov 12 00:10:32.344: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:32.344: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:32.344: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:32.344: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
Nov 12 00:10:32.344: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:32.344: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:32.344: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:32.344: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:32.344: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:32.344: INFO:
Nov 12 00:10:34.341: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:34.341: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:34.341: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:34.341: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
Nov 12 00:10:34.341: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:34.341: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:34.341: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:34.341: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:34.341: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:34.341: INFO:
Nov 12 00:10:36.341: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:36.341: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:36.341: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:36.341: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
Nov 12 00:10:36.341: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:36.341: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:36.341: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:36.341: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:36.341: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:36.341: INFO:
Nov 12 00:10:38.339: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:38.339: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:38.339: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:38.339: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
Nov 12 00:10:38.339: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:38.339: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:38.339: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:38.339: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:38.339: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:38.339: INFO:
Nov 12 00:10:40.340: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:40.340: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:40.340: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:40.340: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
Nov 12 00:10:40.340: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:40.340: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:40.340: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:40.340: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:40.340: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:40.340: INFO:
Nov 12 00:10:42.345: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:42.345: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:42.345: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:42.345: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
Nov 12 00:10:42.345: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:42.345: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:42.345: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:42.345: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:42.345: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:42.345: INFO:
Nov 12 00:10:44.341: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:44.341: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:44.341: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:44.341: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
Nov 12 00:10:44.341: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:44.341: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:44.341: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:44.341: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:44.341: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:44.341: INFO:
Nov 12 00:10:46.359: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:46.359: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:46.359: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:46.359: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
Nov 12 00:10:46.359: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:46.359: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:46.359: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:46.359: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:46.359: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:46.359: INFO:
Nov 12 00:10:48.344: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:48.344: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:48.344: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:48.344: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
Nov 12 00:10:48.344: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:48.344: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:48.344: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:48.344: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:48.344: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:48.344: INFO:
Nov 12 00:10:50.340: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:50.340: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:50.340: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:50.340: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
Nov 12 00:10:50.340: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:50.340: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:50.340: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:50.340: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:50.340: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:50.340: INFO:
Nov 12 00:10:52.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:52.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:52.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:52.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
Nov 12 00:10:52.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:52.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:52.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:52.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:52.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:52.329: INFO:
Nov 12 00:10:54.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:54.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:54.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:54.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
Nov 12 00:10:54.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:54.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:54.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:54.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:54.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:54.328: INFO:
Nov 12 00:10:56.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:56.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:56.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:56.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
Nov 12 00:10:56.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:56.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:56.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:56.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:56.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:56.329: INFO:
Nov 12 00:10:58.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:58.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:58.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:10:58.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
Nov 12 00:10:58.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:10:58.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:10:58.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:58.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:58.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:10:58.327: INFO:
Nov 12 00:11:00.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:00.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:00.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:00.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
Nov 12 00:11:00.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:00.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:00.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:00.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:00.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:00.330: INFO:
Nov 12 00:11:02.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:02.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:02.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:02.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
Nov 12 00:11:02.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:02.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:02.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:02.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:02.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:02.329: INFO:
Nov 12 00:11:04.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:04.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:04.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:04.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
Nov 12 00:11:04.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:04.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:04.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:04.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:04.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:04.329: INFO:
Nov 12 00:11:06.326: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:06.326: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:06.326: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:06.326: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
Nov 12 00:11:06.326: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:06.326: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:06.326: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:06.326: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:06.326: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:06.326: INFO:
Nov 12 00:11:08.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:08.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:08.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:08.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
Nov 12 00:11:08.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:08.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:08.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:08.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:08.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:08.328: INFO:
Nov 12 00:11:10.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:10.332: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:10.332: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:10.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
Nov 12 00:11:10.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:10.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:10.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:10.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:10.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:10.332: INFO:
Nov 12 00:11:12.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:12.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:12.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:12.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
Nov 12 00:11:12.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:12.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:12.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:12.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:12.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:12.327: INFO:
Nov 12 00:11:14.325: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:14.325: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:14.325: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:14.325: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
Nov 12 00:11:14.325: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:14.325: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:14.325: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:14.325: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:14.325: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:14.325: INFO:
Nov 12 00:11:16.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:16.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:16.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:16.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
Nov 12 00:11:16.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:16.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:16.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:16.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:16.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:16.328: INFO:
Nov 12 00:11:18.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:18.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:18.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:18.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
Nov 12 00:11:18.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:18.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:18.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:18.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:18.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:18.329: INFO:
Nov 12 00:11:20.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:20.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:20.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:20.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
Nov 12 00:11:20.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:20.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:20.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:20.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:20.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:20.328: INFO:
Nov 12 00:11:22.326: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:22.326: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:22.326: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:22.326: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
Nov 12 00:11:22.326: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:22.326: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:22.326: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:22.326: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:22.326: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:22.326: INFO:
Nov 12 00:11:24.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:24.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:24.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:24.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
Nov 12 00:11:24.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:24.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:24.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:24.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:24.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:24.330: INFO:
Nov 12 00:11:26.340: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:26.340: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:26.340: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:26.340: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
Nov 12 00:11:26.340: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:26.340: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:26.340: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:26.340: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:26.340: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:26.340: INFO:
Nov 12 00:11:28.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:28.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:28.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:28.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
Nov 12 00:11:28.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:28.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:28.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:28.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:28.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:28.328: INFO:
Nov 12 00:11:30.337: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:30.337: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:30.337: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:30.337: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
Nov 12 00:11:30.337: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:30.337: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:30.337: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:30.337: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:30.337: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:30.337: INFO:
Nov 12 00:11:32.326: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:32.326: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:32.326: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:32.326: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
Nov 12 00:11:32.326: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:32.326: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:32.326: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:32.326: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:32.326: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:32.326: INFO:
Nov 12 00:11:34.339: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:34.339: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:34.339: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:34.339: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
Nov 12 00:11:34.339: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:34.339: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:34.339: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:34.339: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:34.339: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:34.339: INFO:
Nov 12 00:11:36.326: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:36.326: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:36.326: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:36.326: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
Nov 12 00:11:36.326: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:36.326: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:36.326: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:36.326: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:36.326: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:36.326: INFO:
Nov 12 00:11:38.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:38.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:38.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:38.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
Nov 12 00:11:38.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:38.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:38.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:38.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:38.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:38.329: INFO:
Nov 12 00:11:40.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:40.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:40.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:40.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
Nov 12 00:11:40.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:40.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:40.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:40.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:40.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:40.327: INFO:
Nov 12 00:11:42.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:42.332: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:42.332: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:42.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
Nov 12 00:11:42.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:42.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:42.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:42.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:42.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:42.332: INFO:
Nov 12 00:11:44.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:44.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:44.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:44.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
Nov 12 00:11:44.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:44.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:44.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:44.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:44.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:44.328: INFO:
Nov 12 00:11:46.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:46.332: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:46.332: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:46.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
Nov 12 00:11:46.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:46.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:46.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:46.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:46.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:46.332: INFO:
Nov 12 00:11:48.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:48.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:48.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:48.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
Nov 12 00:11:48.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:48.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:48.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:48.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:48.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:48.327: INFO:
Nov 12 00:11:50.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:50.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:50.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:50.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
Nov 12 00:11:50.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:50.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:50.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:50.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:50.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:50.330: INFO:
Nov 12 00:11:52.348: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:52.348: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:52.348: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:52.348: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
Nov 12 00:11:52.348: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:52.348: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:52.348: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:52.348: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:52.348: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:52.348: INFO:
Nov 12 00:11:54.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:54.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:54.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:54.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
Nov 12 00:11:54.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:54.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:54.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:54.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:54.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:54.329: INFO:
Nov 12 00:11:56.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:56.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:56.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:56.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
Nov 12 00:11:56.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:56.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:56.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:56.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:56.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:56.327: INFO:
Nov 12 00:11:58.326: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:58.326: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:58.326: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:11:58.326: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
Nov 12 00:11:58.326: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:11:58.326: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:11:58.326: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:58.326: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:58.326: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:11:58.326: INFO:
Nov 12 00:12:00.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:00.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:00.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:00.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
Nov 12 00:12:00.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:00.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:00.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:00.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:00.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:00.327: INFO:
Nov 12 00:12:02.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:02.331: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:02.331: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:02.331: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
Nov 12 00:12:02.331: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:02.331: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:02.331: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:02.331: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:02.331: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:02.331: INFO:
Nov 12 00:12:04.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:04.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:04.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:04.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
Nov 12 00:12:04.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:04.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:04.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:04.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:04.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:04.328: INFO:
Nov 12 00:12:06.331: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:06.331: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:06.331: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:06.331: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
Nov 12 00:12:06.331: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:06.331: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:06.331: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:06.331: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:06.331: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:06.331: INFO:
Nov 12 00:12:08.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:08.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:08.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:08.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
Nov 12 00:12:08.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:08.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:08.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:08.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:08.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:08.327: INFO:
Nov 12 00:12:10.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:10.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:10.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:10.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
Nov 12 00:12:10.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:10.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:10.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:10.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:10.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:10.328: INFO:
Nov 12 00:12:12.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:12.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:12.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:12.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
Nov 12 00:12:12.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:12.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:12.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:12.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:12.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:12.330: INFO:
Nov 12 00:12:14.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:14.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:14.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:14.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
Nov 12 00:12:14.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:14.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:14.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:14.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:14.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:14.330: INFO:
Nov 12 00:12:16.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:16.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:16.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:16.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
Nov 12 00:12:16.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:16.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:16.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:16.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:16.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:16.328: INFO:
Nov 12 00:12:18.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:18.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:18.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:18.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
Nov 12 00:12:18.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:18.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:18.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:18.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:18.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:18.329: INFO:
Nov 12 00:12:20.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:20.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:20.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:20.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
Nov 12 00:12:20.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:20.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:20.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:20.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:20.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:20.328: INFO:
Nov 12 00:12:22.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:22.332: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:22.332: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:22.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
Nov 12 00:12:22.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:22.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:22.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:22.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:22.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:22.332: INFO:
Nov 12 00:12:24.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:24.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:24.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:24.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
Nov 12 00:12:24.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:24.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:24.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:24.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:24.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:24.327: INFO:
Nov 12 00:12:26.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:26.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:26.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:26.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
Nov 12 00:12:26.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:26.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:26.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:26.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:26.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:26.328: INFO:
Nov 12 00:12:28.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:28.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:28.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:28.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
Nov 12 00:12:28.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:28.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:28.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:28.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:28.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:28.327: INFO:
Nov 12 00:12:30.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:30.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:30.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:30.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
Nov 12 00:12:30.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:30.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:30.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:30.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:30.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:30.327: INFO:
Nov 12 00:12:32.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:32.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:32.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:32.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
Nov 12 00:12:32.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:32.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:32.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:32.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:32.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:32.329: INFO:
Nov 12 00:12:34.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:34.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:34.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:34.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
Nov 12 00:12:34.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:34.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:34.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:34.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:34.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:34.329: INFO:
Nov 12 00:12:36.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:36.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:36.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:36.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
Nov 12 00:12:36.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:36.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:36.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:36.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:36.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:36.328: INFO:
Nov 12 00:12:38.336: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:38.336: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:38.336: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:38.336: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
Nov 12 00:12:38.336: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:38.336: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:38.336: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:38.336: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:38.336: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:38.336: INFO:
Nov 12 00:12:40.351: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:40.351: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:40.351: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:40.351: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
Nov 12 00:12:40.352: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:40.352: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:40.352: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:40.352: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:40.352: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:40.352: INFO:
Nov 12 00:12:42.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:42.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:42.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:42.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
Nov 12 00:12:42.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:42.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:42.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:42.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:42.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:42.329: INFO:
Nov 12 00:12:44.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:44.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:44.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:44.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
Nov 12 00:12:44.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:44.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:44.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:44.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:44.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:44.327: INFO:
Nov 12 00:12:46.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:46.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:46.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:46.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
Nov 12 00:12:46.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:46.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:46.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:46.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:46.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:46.328: INFO:
Nov 12 00:12:48.333: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:48.333: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:48.333: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:48.333: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
Nov 12 00:12:48.333: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:48.333: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:48.333: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:48.333: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:48.333: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:48.333: INFO:
Nov 12 00:12:50.339: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:50.339: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:50.339: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:50.339: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
Nov 12 00:12:50.339: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:50.339: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:50.339: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:50.339: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:50.339: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:50.339: INFO:
Nov 12 00:12:52.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:52.332: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:52.332: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:52.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
Nov 12 00:12:52.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:52.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:52.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:52.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:52.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:52.332: INFO:
Nov 12 00:12:54.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:54.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:54.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:54.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
Nov 12 00:12:54.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:54.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:54.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:54.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:54.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:54.330: INFO:
Nov 12 00:12:56.326: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:56.326: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:56.326: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:56.326: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
Nov 12 00:12:56.326: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:56.326: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:56.326: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:56.326: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:56.326: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:56.326: INFO:
Nov 12 00:12:58.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:58.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:58.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:12:58.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
Nov 12 00:12:58.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:12:58.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:12:58.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:58.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:58.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:12:58.328: INFO:
Nov 12 00:13:00.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:00.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:00.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:00.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
Nov 12 00:13:00.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:00.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:00.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:00.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:00.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:00.329: INFO:
Nov 12 00:13:02.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:02.332: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:02.332: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:02.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
Nov 12 00:13:02.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:02.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:02.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:02.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:02.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:02.332: INFO:
Nov 12 00:13:04.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:04.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:04.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:04.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
Nov 12 00:13:04.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:04.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:04.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:04.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:04.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:04.327: INFO:
Nov 12 00:13:06.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:06.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:06.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:06.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
Nov 12 00:13:06.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:06.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:06.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:06.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:06.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:06.327: INFO:
Nov 12 00:13:08.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:08.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:08.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:08.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
Nov 12 00:13:08.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:08.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:08.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:08.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:08.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:08.327: INFO:
Nov 12 00:13:10.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:10.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:10.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:10.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
Nov 12 00:13:10.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:10.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:10.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:10.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:10.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:10.328: INFO:
Nov 12 00:13:12.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:12.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:12.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:12.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
Nov 12 00:13:12.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:12.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:12.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:12.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:12.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:12.327: INFO:
Nov 12 00:13:14.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:14.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:14.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:14.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
Nov 12 00:13:14.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:14.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:14.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:14.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:14.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:14.327: INFO:
Nov 12 00:13:16.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:16.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:16.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:16.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
Nov 12 00:13:16.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:16.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:16.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:16.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:16.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:16.327: INFO:
Nov 12 00:13:18.338: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:18.338: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:18.338: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:18.338: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
Nov 12 00:13:18.338: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:18.338: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:18.338: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:18.338: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:18.338: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:18.338: INFO:
Nov 12 00:13:20.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:20.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:20.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:20.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
Nov 12 00:13:20.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:20.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:20.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:20.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:20.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:20.328: INFO:
Nov 12 00:13:22.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:22.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:22.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:22.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
Nov 12 00:13:22.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:22.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:22.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:22.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:22.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:22.328: INFO:
Nov 12 00:13:24.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:24.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:24.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:24.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
Nov 12 00:13:24.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:24.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:24.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:24.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:24.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:24.328: INFO:
Nov 12 00:13:26.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:26.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:26.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:26.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
Nov 12 00:13:26.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:26.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:26.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:26.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:26.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:26.329: INFO:
Nov 12 00:13:28.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:28.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:28.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:28.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
Nov 12 00:13:28.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:28.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:28.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:28.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:28.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:28.329: INFO:
Nov 12 00:13:30.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:30.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:30.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:30.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
Nov 12 00:13:30.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:30.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:30.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:30.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:30.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:30.330: INFO:
Nov 12 00:13:32.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:32.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:32.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:32.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
Nov 12 00:13:32.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:32.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:32.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:32.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:32.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:32.328: INFO:
Nov 12 00:13:34.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:34.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:34.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:34.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
Nov 12 00:13:34.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:34.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:34.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:34.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:34.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:34.327: INFO:
Nov 12 00:13:36.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:36.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:36.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:36.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
Nov 12 00:13:36.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:36.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:36.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:36.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:36.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:36.327: INFO:
Nov 12 00:13:38.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:38.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:38.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:38.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
Nov 12 00:13:38.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:38.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:38.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:38.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:38.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:38.329: INFO:
Nov 12 00:13:40.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:40.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:40.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:40.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
Nov 12 00:13:40.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:40.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:40.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:40.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:40.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:40.327: INFO:
Nov 12 00:13:42.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:42.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:42.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:42.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
Nov 12 00:13:42.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:42.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:42.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:42.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:42.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:42.329: INFO:
Nov 12 00:13:44.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:44.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:44.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:44.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
Nov 12 00:13:44.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:44.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:44.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:44.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:44.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:44.327: INFO:
Nov 12 00:13:46.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:46.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:46.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:46.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
Nov 12 00:13:46.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:46.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:46.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:46.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:46.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:46.329: INFO:
Nov 12 00:13:48.332: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:48.332: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:48.332: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:48.332: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
Nov 12 00:13:48.332: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:48.332: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:48.332: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:48.332: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:48.332: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:48.332: INFO:
Nov 12 00:13:50.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:50.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:50.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:50.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
Nov 12 00:13:50.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:50.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:50.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:50.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:50.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:50.327: INFO:
Nov 12 00:13:52.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:52.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:52.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:52.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
Nov 12 00:13:52.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:52.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:52.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:52.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:52.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:52.328: INFO:
Nov 12 00:13:54.444: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:54.444: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:54.444: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:54.444: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
Nov 12 00:13:54.444: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:54.444: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:54.444: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:54.444: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:54.444: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:54.444: INFO:
Nov 12 00:13:56.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:56.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:56.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:56.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
Nov 12 00:13:56.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:56.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:56.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:56.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:56.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:56.329: INFO:
Nov 12 00:13:58.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:58.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:58.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:13:58.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
Nov 12 00:13:58.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:13:58.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:13:58.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:58.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:58.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:13:58.327: INFO:
Nov 12 00:14:00.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:00.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:00.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:00.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
Nov 12 00:14:00.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:14:00.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:14:00.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:00.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:00.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:00.329: INFO:
Nov 12 00:14:02.329: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:02.329: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:02.329: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:02.329: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
Nov 12 00:14:02.329: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:14:02.329: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:14:02.329: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:02.329: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:02.329: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:02.329: INFO:
Nov 12 00:14:04.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:04.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:04.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:04.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
Nov 12 00:14:04.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:14:04.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:14:04.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:04.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:04.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:04.327: INFO:
Nov 12 00:14:06.330: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:06.330: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:06.330: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:06.330: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
Nov 12 00:14:06.330: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:14:06.330: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:14:06.330: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:06.330: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:06.330: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:06.330: INFO:
Nov 12 00:14:08.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:08.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:08.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:08.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
Nov 12 00:14:08.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:14:08.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:14:08.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:08.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:08.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:08.328: INFO:
Nov 12 00:14:10.338: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:10.338: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:10.338: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:10.338: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
Nov 12 00:14:10.338: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:14:10.338: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:14:10.338: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:10.338: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:10.338: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:10.338: INFO:
Nov 12 00:14:12.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:12.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:12.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:12.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
Nov 12 00:14:12.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:14:12.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:14:12.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:12.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:12.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:12.327: INFO:
Nov 12 00:14:14.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:14.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:14.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:14.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Nov 12 00:14:14.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:14:14.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:14:14.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:14.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:14.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:14.328: INFO:
Nov 12 00:14:16.328: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:16.328: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:16.328: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:16.328: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Nov 12 00:14:16.328: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:14:16.328: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:14:16.328: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:16.328: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:16.328: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:16.328: INFO:
Nov 12 00:14:18.327: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:18.327: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:18.327: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:18.327: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 12 00:14:18.327: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:14:18.327: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:14:18.327: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:18.327: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:18.327: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:18.327: INFO:
Nov 12 00:14:18.458: INFO: The status of Pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:18.458: INFO: The status of Pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:18.458: INFO: The status of Pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 12 00:14:18.458: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 12 00:14:18.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 12 00:14:18.458: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:14:18.458: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:18.458: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:18.458: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:18.458: INFO:
�[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m11/12/22 00:14:18.458�[0m
�[1mSTEP:�[0m Found 133 events. �[38;5;243m11/12/22 00:14:18.511�[0m
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:11 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-ghmn83-control-plane-cfthd_8abe2ec3-a74e-493c-89ba-2ff979004e2d became leader
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:11 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-ghmn83-control-plane-cfthd_daf24a6f-17a7-4e1d-803f-d90620540b34 became leader
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:16 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-64475449fc to 2
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:16 +0000 UTC - event for etcd-capz-conf-ghmn83-control-plane-cfthd: {node-controller } NodeNotReady: Node is not ready
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:17 +0000 UTC - event for coredns-64475449fc: {replicaset-controller } SuccessfulCreate: Created pod: coredns-64475449fc-zvt7m
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:17 +0000 UTC - event for coredns-64475449fc: {replicaset-controller } SuccessfulCreate: Created pod: coredns-64475449fc-stlx5
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:17 +0000 UTC - event for coredns-64475449fc-stlx5: {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 12 00:14:18.511: INFO: At 2022-11-12 00:00:17 +0000 UTC - event for coredns-64475449fc-zvt7m: {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 12 00:14:18.511: INFO: At 2022-11-12 00:00:17 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-tnq7v
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:17 +0000 UTC - event for kube-proxy-tnq7v: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-tnq7v to capz-conf-ghmn83-control-plane-cfthd
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:18 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulDelete: Deleted pod: kube-proxy-tnq7v
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:18 +0000 UTC - event for kube-proxy-tnq7v: {kubelet capz-conf-ghmn83-control-plane-cfthd} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:20 +0000 UTC - event for kube-proxy-tnq7v: {kubelet capz-conf-ghmn83-control-plane-cfthd} Pulled: Container image "gcr.io/k8s-staging-ci-images/kube-proxy:v1.26.0-beta.0.30_e4d46148de9d83" already present on machine
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:20 +0000 UTC - event for kube-proxy-tnq7v: {kubelet capz-conf-ghmn83-control-plane-cfthd} Created: Created container kube-proxy
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:20 +0000 UTC - event for kube-proxy-tnq7v: {kubelet capz-conf-ghmn83-control-plane-cfthd} Started: Started container kube-proxy
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:21 +0000 UTC - event for kube-proxy-tnq7v: {kubelet capz-conf-ghmn83-control-plane-cfthd} Killing: Stopping container kube-proxy
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:23 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-xvfvk
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:23 +0000 UTC - event for kube-proxy-xvfvk: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-xvfvk to capz-conf-ghmn83-control-plane-cfthd
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:24 +0000 UTC - event for kube-proxy-xvfvk: {kubelet capz-conf-ghmn83-control-plane-cfthd} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.59_0997f9c364c4bc"
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:25 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-954b56d74 to 1
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:25 +0000 UTC - event for metrics-server-954b56d74: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-954b56d74-gzfdm
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:25 +0000 UTC - event for metrics-server-954b56d74-gzfdm: {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 12 00:14:18.511: INFO: At 2022-11-12 00:00:26 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-56c5ff4bf8 to 1
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:26 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-56c5ff4bf8-2mrcx
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:26 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-2mrcx: {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 12 00:14:18.511: INFO: At 2022-11-12 00:00:26 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-dk2fv
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:26 +0000 UTC - event for calico-node-dk2fv: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-dk2fv to capz-conf-ghmn83-control-plane-cfthd
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:27 +0000 UTC - event for calico-node-dk2fv: {kubelet capz-conf-ghmn83-control-plane-cfthd} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:28 +0000 UTC - event for kube-proxy-xvfvk: {kubelet capz-conf-ghmn83-control-plane-cfthd} Created: Created container kube-proxy
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:28 +0000 UTC - event for kube-proxy-xvfvk: {kubelet capz-conf-ghmn83-control-plane-cfthd} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.59_0997f9c364c4bc" in 4.685933587s (4.686061866s including waiting)
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:29 +0000 UTC - event for kube-proxy-xvfvk: {kubelet capz-conf-ghmn83-control-plane-cfthd} Started: Started container kube-proxy
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:37 +0000 UTC - event for calico-node-dk2fv: {kubelet capz-conf-ghmn83-control-plane-cfthd} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 9.076532098s (10.37679292s including waiting)
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:37 +0000 UTC - event for calico-node-dk2fv: {kubelet capz-conf-ghmn83-control-plane-cfthd} Created: Created container upgrade-ipam
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:38 +0000 UTC - event for calico-node-dk2fv: {kubelet capz-conf-ghmn83-control-plane-cfthd} Started: Started container upgrade-ipam
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:41 +0000 UTC - event for calico-node-dk2fv: {kubelet capz-conf-ghmn83-control-plane-cfthd} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:41 +0000 UTC - event for calico-node-dk2fv: {kubelet capz-conf-ghmn83-control-plane-cfthd} Started: Started container install-cni
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:41 +0000 UTC - event for calico-node-dk2fv: {kubelet capz-conf-ghmn83-control-plane-cfthd} Created: Created container install-cni
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:44 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-2mrcx: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-56c5ff4bf8-2mrcx to capz-conf-ghmn83-control-plane-cfthd
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:44 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-2mrcx: {kubelet capz-conf-ghmn83-control-plane-cfthd} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "57894adce7b3b1b26ed12e6d53a64980e4f4cbc6199beaa6360e268f7282b444": 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 12 00:14:18.511: INFO: At 2022-11-12 00:00:44 +0000 UTC - event for calico-node-dk2fv: {kubelet capz-conf-ghmn83-control-plane-cfthd} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:44 +0000 UTC - event for coredns-64475449fc-stlx5: {kubelet capz-conf-ghmn83-control-plane-cfthd} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "ce0cd0153b659b41c2c1cb7aeaaa20791c59155cc6ed681fd303660f1af60db5": 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 12 00:14:18.511: INFO: At 2022-11-12 00:00:44 +0000 UTC - event for coredns-64475449fc-stlx5: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-64475449fc-stlx5 to capz-conf-ghmn83-control-plane-cfthd
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:44 +0000 UTC - event for coredns-64475449fc-zvt7m: {kubelet capz-conf-ghmn83-control-plane-cfthd} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "c727b22dc6b3f46648143559369419aec762993015dd24cad879c07d72c0c82a": 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 12 00:14:18.511: INFO: At 2022-11-12 00:00:44 +0000 UTC - event for coredns-64475449fc-zvt7m: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-64475449fc-zvt7m to capz-conf-ghmn83-control-plane-cfthd
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:44 +0000 UTC - event for metrics-server-954b56d74-gzfdm: {kubelet capz-conf-ghmn83-control-plane-cfthd} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "179ac6cf682f524650ab4269d696eb536b1e14323d07beea537042b50d4edfdc": 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 12 00:14:18.511: INFO: At 2022-11-12 00:00:44 +0000 UTC - event for metrics-server-954b56d74-gzfdm: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-954b56d74-gzfdm to capz-conf-ghmn83-control-plane-cfthd
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:54 +0000 UTC - event for calico-node-dk2fv: {kubelet capz-conf-ghmn83-control-plane-cfthd} Started: Started container calico-node
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:54 +0000 UTC - event for calico-node-dk2fv: {kubelet capz-conf-ghmn83-control-plane-cfthd} Created: Created container calico-node
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:54 +0000 UTC - event for calico-node-dk2fv: {kubelet capz-conf-ghmn83-control-plane-cfthd} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 10.297126315s (10.297152314s including waiting)
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:55 +0000 UTC - event for calico-node-dk2fv: {kubelet capz-conf-ghmn83-control-plane-cfthd} 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 12 00:14:18.511: INFO: At 2022-11-12 00:00:58 +0000 UTC - event for coredns-64475449fc-stlx5: {kubelet capz-conf-ghmn83-control-plane-cfthd} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:58 +0000 UTC - event for coredns-64475449fc-stlx5: {kubelet capz-conf-ghmn83-control-plane-cfthd} Created: Created container coredns
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:58 +0000 UTC - event for coredns-64475449fc-zvt7m: {kubelet capz-conf-ghmn83-control-plane-cfthd} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:58 +0000 UTC - event for coredns-64475449fc-zvt7m: {kubelet capz-conf-ghmn83-control-plane-cfthd} Created: Created container coredns
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:58 +0000 UTC - event for metrics-server-954b56d74-gzfdm: {kubelet capz-conf-ghmn83-control-plane-cfthd} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:59 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-2mrcx: {kubelet capz-conf-ghmn83-control-plane-cfthd} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0"
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:59 +0000 UTC - event for coredns-64475449fc-stlx5: {kubelet capz-conf-ghmn83-control-plane-cfthd} Unhealthy: Readiness probe failed: Get "http://192.168.209.1:8181/ready": dial tcp 192.168.209.1:8181: connect: connection refused
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:59 +0000 UTC - event for coredns-64475449fc-stlx5: {kubelet capz-conf-ghmn83-control-plane-cfthd} Started: Started container coredns
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:59 +0000 UTC - event for coredns-64475449fc-zvt7m: {kubelet capz-conf-ghmn83-control-plane-cfthd} Unhealthy: Readiness probe failed: Get "http://192.168.209.2:8181/ready": dial tcp 192.168.209.2:8181: connect: connection refused
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:00:59 +0000 UTC - event for coredns-64475449fc-zvt7m: {kubelet capz-conf-ghmn83-control-plane-cfthd} Started: Started container coredns
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:01:04 +0000 UTC - event for metrics-server-954b56d74-gzfdm: {kubelet capz-conf-ghmn83-control-plane-cfthd} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 5.79830668s (5.799022754s including waiting)
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:01:04 +0000 UTC - event for metrics-server-954b56d74-gzfdm: {kubelet capz-conf-ghmn83-control-plane-cfthd} Created: Created container metrics-server
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:01:04 +0000 UTC - event for metrics-server-954b56d74-gzfdm: {kubelet capz-conf-ghmn83-control-plane-cfthd} Started: Started container metrics-server
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:01:11 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-2mrcx: {kubelet capz-conf-ghmn83-control-plane-cfthd} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 7.359771409s (12.42984861s including waiting)
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:01:11 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-2mrcx: {kubelet capz-conf-ghmn83-control-plane-cfthd} Created: Created container calico-kube-controllers
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:01:12 +0000 UTC - event for calico-kube-controllers-56c5ff4bf8-2mrcx: {kubelet capz-conf-ghmn83-control-plane-cfthd} Started: Started container calico-kube-controllers
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:05 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-tqsl4
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:05 +0000 UTC - event for calico-node-windows-tqsl4: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-tqsl4 to capz-conf-cm7pj
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:05 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-vg54t
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:05 +0000 UTC - event for containerd-logger-vg54t: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-vg54t to capz-conf-cm7pj
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:05 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-2hth8
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:05 +0000 UTC - event for kube-proxy-windows-2hth8: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-2hth8 to capz-conf-cm7pj
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:07 +0000 UTC - event for calico-node-windows-tqsl4: {kubelet capz-conf-cm7pj} FailedMount: MountVolume.SetUp failed for volume "kubeadm-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:07 +0000 UTC - event for calico-node-windows-tqsl4: {kubelet capz-conf-cm7pj} FailedMount: MountVolume.SetUp failed for volume "calico-config-windows" : failed to sync configmap cache: timed out waiting for the condition
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:10 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-wtrbt
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:10 +0000 UTC - event for calico-node-windows-wtrbt: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-wtrbt to capz-conf-ld5bg
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:10 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-vhvkr
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:10 +0000 UTC - event for containerd-logger-vhvkr: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-vhvkr to capz-conf-ld5bg
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:10 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-lrqbz
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:10 +0000 UTC - event for kube-proxy-windows-lrqbz: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-lrqbz to capz-conf-ld5bg
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:12 +0000 UTC - event for kube-proxy-windows-lrqbz: {kubelet capz-conf-ld5bg} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:23 +0000 UTC - event for calico-node-windows-tqsl4: {kubelet capz-conf-cm7pj} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:23 +0000 UTC - event for containerd-logger-vg54t: {kubelet capz-conf-cm7pj} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:23 +0000 UTC - event for kube-proxy-windows-2hth8: {kubelet capz-conf-cm7pj} Created: Created container kube-proxy
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:23 +0000 UTC - event for kube-proxy-windows-2hth8: {kubelet capz-conf-cm7pj} Pulled: Container image "sigwindowstools/kube-proxy:v1.26.0-beta.0.30_e4d46148de9d83-calico-hostprocess" already present on machine
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:24 +0000 UTC - event for kube-proxy-windows-2hth8: {kubelet capz-conf-cm7pj} Started: Started container kube-proxy
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:27 +0000 UTC - event for containerd-logger-vg54t: {kubelet capz-conf-cm7pj} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 3.4531543s (3.4531543s including waiting)
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:29 +0000 UTC - event for calico-node-windows-wtrbt: {kubelet capz-conf-ld5bg} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:29 +0000 UTC - event for containerd-logger-vhvkr: {kubelet capz-conf-ld5bg} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:29 +0000 UTC - event for kube-proxy-windows-lrqbz: {kubelet capz-conf-ld5bg} Started: Started container kube-proxy
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:29 +0000 UTC - event for kube-proxy-windows-lrqbz: {kubelet capz-conf-ld5bg} Created: Created container kube-proxy
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:29 +0000 UTC - event for kube-proxy-windows-lrqbz: {kubelet capz-conf-ld5bg} Pulled: Container image "sigwindowstools/kube-proxy:v1.26.0-beta.0.30_e4d46148de9d83-calico-hostprocess" already present on machine
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:32 +0000 UTC - event for calico-node-windows-tqsl4: {kubelet capz-conf-cm7pj} Created: Created container install-cni
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:32 +0000 UTC - event for calico-node-windows-tqsl4: {kubelet capz-conf-cm7pj} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 5.5216292s (8.9529059s including waiting)
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:33 +0000 UTC - event for calico-node-windows-tqsl4: {kubelet capz-conf-cm7pj} Started: Started container install-cni
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:34 +0000 UTC - event for calico-node-windows-wtrbt: {kubelet capz-conf-ld5bg} Created: Created container install-cni
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:34 +0000 UTC - event for calico-node-windows-wtrbt: {kubelet capz-conf-ld5bg} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 5.2441632s (5.2441632s including waiting)
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:34 +0000 UTC - event for calico-node-windows-wtrbt: {kubelet capz-conf-ld5bg} Started: Started container install-cni
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:35 +0000 UTC - event for containerd-logger-vg54t: {kubelet capz-conf-cm7pj} Created: Created container containerd-logger
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:35 +0000 UTC - event for containerd-logger-vg54t: {kubelet capz-conf-cm7pj} Started: Started container containerd-logger
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:35 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-c6bkc
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:35 +0000 UTC - event for csi-proxy-c6bkc: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-c6bkc to capz-conf-cm7pj
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:36 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-hq2bc
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:36 +0000 UTC - event for csi-proxy-c6bkc: {kubelet capz-conf-cm7pj} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:36 +0000 UTC - event for csi-proxy-hq2bc: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-hq2bc to capz-conf-ld5bg
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:37 +0000 UTC - event for csi-proxy-hq2bc: {kubelet capz-conf-ld5bg} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:38 +0000 UTC - event for calico-node-windows-tqsl4: {kubelet capz-conf-cm7pj} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:38 +0000 UTC - event for containerd-logger-vhvkr: {kubelet capz-conf-ld5bg} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 4.5757056s (9.7475417s including waiting)
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:39 +0000 UTC - event for calico-node-windows-wtrbt: {kubelet capz-conf-ld5bg} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:45 +0000 UTC - event for containerd-logger-vhvkr: {kubelet capz-conf-ld5bg} Created: Created container containerd-logger
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:45 +0000 UTC - event for containerd-logger-vhvkr: {kubelet capz-conf-ld5bg} Started: Started container containerd-logger
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:51 +0000 UTC - event for csi-proxy-c6bkc: {kubelet capz-conf-cm7pj} Started: Started container csi-proxy
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:51 +0000 UTC - event for csi-proxy-c6bkc: {kubelet capz-conf-cm7pj} Created: Created container csi-proxy
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:51 +0000 UTC - event for csi-proxy-c6bkc: {kubelet capz-conf-cm7pj} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 14.9364542s (14.9364542s including waiting)
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:54 +0000 UTC - event for calico-node-windows-tqsl4: {kubelet capz-conf-cm7pj} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 364.5134ms (364.5134ms including waiting)
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:54 +0000 UTC - event for calico-node-windows-tqsl4: {kubelet capz-conf-cm7pj} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 3.1220605s (15.8634517s including waiting)
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:54 +0000 UTC - event for calico-node-windows-tqsl4: {kubelet capz-conf-cm7pj} Created: Created container calico-node-startup
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:54 +0000 UTC - event for calico-node-windows-tqsl4: {kubelet capz-conf-cm7pj} Started: Started container calico-node-startup
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:54 +0000 UTC - event for calico-node-windows-tqsl4: {kubelet capz-conf-cm7pj} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:54 +0000 UTC - event for csi-proxy-hq2bc: {kubelet capz-conf-ld5bg} Created: Created container csi-proxy
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:54 +0000 UTC - event for csi-proxy-hq2bc: {kubelet capz-conf-ld5bg} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 15.004324s (16.7654006s including waiting)
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:54 +0000 UTC - event for csi-proxy-hq2bc: {kubelet capz-conf-ld5bg} Started: Started container csi-proxy
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:58 +0000 UTC - event for calico-node-windows-wtrbt: {kubelet capz-conf-ld5bg} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:58 +0000 UTC - event for calico-node-windows-wtrbt: {kubelet capz-conf-ld5bg} Started: Started container calico-node-startup
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:58 +0000 UTC - event for calico-node-windows-wtrbt: {kubelet capz-conf-ld5bg} Created: Created container calico-node-startup
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:58 +0000 UTC - event for calico-node-windows-wtrbt: {kubelet capz-conf-ld5bg} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 4.656335s (19.044526s including waiting)
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:03:59 +0000 UTC - event for calico-node-windows-wtrbt: {kubelet capz-conf-ld5bg} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 637.7412ms (637.7412ms including waiting)
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:04:00 +0000 UTC - event for calico-node-windows-tqsl4: {kubelet capz-conf-cm7pj} Created: Created container calico-node-felix
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:04:01 +0000 UTC - event for calico-node-windows-tqsl4: {kubelet capz-conf-cm7pj} Started: Started container calico-node-felix
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:04:05 +0000 UTC - event for calico-node-windows-wtrbt: {kubelet capz-conf-ld5bg} Created: Created container calico-node-felix
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:04:05 +0000 UTC - event for calico-node-windows-wtrbt: {kubelet capz-conf-ld5bg} Started: Started container calico-node-felix
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:04:23 +0000 UTC - event for calico-node-windows-tqsl4: {kubelet capz-conf-cm7pj} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 405.1438ms (405.1438ms including waiting)
Nov 12 00:14:18.511: INFO: At 2022-11-12 00:04:27 +0000 UTC - event for calico-node-windows-wtrbt: {kubelet capz-conf-ld5bg} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 386.333ms (386.333ms including waiting)
Nov 12 00:14:18.567: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 12 00:14:18.567: INFO: calico-kube-controllers-56c5ff4bf8-2mrcx capz-conf-ghmn83-control-plane-cfthd Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:44 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:01:12 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:01:12 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:44 +0000 UTC }]
Nov 12 00:14:18.567: INFO: calico-node-dk2fv capz-conf-ghmn83-control-plane-cfthd Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:44 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:57 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:57 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:26 +0000 UTC }]
Nov 12 00:14:18.567: INFO: calico-node-windows-tqsl4 capz-conf-cm7pj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:38 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:04:28 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:04:28 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:05 +0000 UTC }]
Nov 12 00:14:18.567: INFO: calico-node-windows-wtrbt capz-conf-ld5bg Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:39 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:04:33 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:04:33 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:10 +0000 UTC }]
Nov 12 00:14:18.567: INFO: containerd-logger-vg54t capz-conf-cm7pj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:06 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:36 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:36 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:05 +0000 UTC }]
Nov 12 00:14:18.567: INFO: containerd-logger-vhvkr capz-conf-ld5bg Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:10 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:45 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:45 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:10 +0000 UTC }]
Nov 12 00:14:18.567: INFO: coredns-64475449fc-stlx5 capz-conf-ghmn83-control-plane-cfthd Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:44 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:01:00 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:01:00 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:44 +0000 UTC }]
Nov 12 00:14:18.567: INFO: coredns-64475449fc-zvt7m capz-conf-ghmn83-control-plane-cfthd Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:44 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:01:00 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:01:00 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:44 +0000 UTC }]
Nov 12 00:14:18.567: INFO: csi-proxy-c6bkc capz-conf-cm7pj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:35 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:52 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:52 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:35 +0000 UTC }]
Nov 12 00:14:18.567: INFO: csi-proxy-hq2bc capz-conf-ld5bg Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:36 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:54 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:54 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:36 +0000 UTC }]
Nov 12 00:14:18.567: INFO: etcd-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 23:59:53 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:19 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:19 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-11 23:59:53 +0000 UTC }]
Nov 12 00:14:18.567: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:18.567: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:18.567: INFO: kube-proxy-windows-2hth8 capz-conf-cm7pj Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:06 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:24 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:24 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:05 +0000 UTC }]
Nov 12 00:14:18.567: INFO: kube-proxy-windows-lrqbz capz-conf-ld5bg Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:10 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:30 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:30 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:03:10 +0000 UTC }]
Nov 12 00:14:18.567: INFO: kube-proxy-xvfvk capz-conf-ghmn83-control-plane-cfthd Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:23 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:29 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:29 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:23 +0000 UTC }]
Nov 12 00:14:18.567: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
Nov 12 00:14:18.567: INFO: metrics-server-954b56d74-gzfdm capz-conf-ghmn83-control-plane-cfthd Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:44 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:01:24 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:01:24 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-12 00:00:44 +0000 UTC }]
Nov 12 00:14:18.567: INFO:
Nov 12 00:14:19.045: INFO:
Logging node info for node capz-conf-cm7pj
Nov 12 00:14:19.236: INFO: Node Info: &Node{ObjectMeta:{capz-conf-cm7pj 7a1af3b8-c71d-42af-8f2e-787b1b7ce0e7 1581 0 2022-11-12 00:03:05 +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-cm7pj 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-ghmn83 cluster.x-k8s.io/cluster-namespace:capz-conf-ghmn83 cluster.x-k8s.io/machine:capz-conf-ghmn83-md-win-66545b4fbb-s7fcm cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-ghmn83-md-win-66545b4fbb 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.172.129 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:92:05:02 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet.exe Update v1 2022-11-12 00:03:05 +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-12 00:03:06 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kube-controller-manager Update v1 2022-11-12 00:03:35 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-12 00:04:14 +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-12 00:04:20 +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-12 00:09:12 +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-ghmn83/providers/Microsoft.Compute/virtualMachines/capz-conf-cm7pj,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-12 00:09:12 +0000 UTC,LastTransitionTime:2022-11-12 00:03:05 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-12 00:09:12 +0000 UTC,LastTransitionTime:2022-11-12 00:03:05 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-12 00:09:12 +0000 UTC,LastTransitionTime:2022-11-12 00:03:05 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-12 00:09:12 +0000 UTC,LastTransitionTime:2022-11-12 00:03:35 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-cm7pj,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-cm7pj,SystemUUID:B09F491F-5055-4021-A128-C982FEDEA633,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.26.0-beta.0.59+0997f9c364c4bc-dirty,KubeProxyVersion:v1.26.0-beta.0.59+0997f9c364c4bc-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.26.0-beta.0.30_e4d46148de9d83-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 12 00:14:19.236: INFO:
Logging kubelet events for node capz-conf-cm7pj
Nov 12 00:14:19.435: INFO:
Logging pods the kubelet thinks is on node capz-conf-cm7pj
Nov 12 00:14:19.652: INFO: kube-proxy-windows-2hth8 started at 2022-11-12 00:03:06 +0000 UTC (0+1 container statuses recorded)
Nov 12 00:14:19.652: INFO: Container kube-proxy ready: true, restart count 0
Nov 12 00:14:19.652: INFO: csi-proxy-c6bkc started at 2022-11-12 00:03:35 +0000 UTC (0+1 container statuses recorded)
Nov 12 00:14:19.652: INFO: Container csi-proxy ready: true, restart count 0
Nov 12 00:14:19.652: INFO: calico-node-windows-tqsl4 started at 2022-11-12 00:03:06 +0000 UTC (1+2 container statuses recorded)
Nov 12 00:14:19.652: INFO: Init container install-cni ready: true, restart count 0
Nov 12 00:14:19.652: INFO: Container calico-node-felix ready: true, restart count 1
Nov 12 00:14:19.652: INFO: Container calico-node-startup ready: true, restart count 0
Nov 12 00:14:19.652: INFO: containerd-logger-vg54t started at 2022-11-12 00:03:06 +0000 UTC (0+1 container statuses recorded)
Nov 12 00:14:19.652: INFO: Container containerd-logger ready: true, restart count 0
Nov 12 00:14:20.290: INFO:
Latency metrics for node capz-conf-cm7pj
Nov 12 00:14:20.290: INFO:
Logging node info for node capz-conf-ghmn83-control-plane-cfthd
Nov 12 00:14:20.436: INFO: Node Info: &Node{ObjectMeta:{capz-conf-ghmn83-control-plane-cfthd 2f8a5de7-49dd-4f0b-bae7-80a29594a63d 1788 0 2022-11-12 00:00:14 +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-2 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-ghmn83-control-plane-cfthd 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-2] map[cluster.x-k8s.io/cluster-name:capz-conf-ghmn83 cluster.x-k8s.io/cluster-namespace:capz-conf-ghmn83 cluster.x-k8s.io/machine:capz-conf-ghmn83-control-plane-l82ph cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-ghmn83-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.209.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2022-11-12 00:00:14 +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-12 00:00:15 +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-12 00:00:23 +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-12 00:00:44 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2022-11-12 00:00:55 +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-12 00:11:29 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-ghmn83/providers/Microsoft.Compute/virtualMachines/capz-conf-ghmn83-control-plane-cfthd,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-12 00:00:55 +0000 UTC,LastTransitionTime:2022-11-12 00:00:55 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-12 00:11:29 +0000 UTC,LastTransitionTime:2022-11-11 23:59:53 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-12 00:11:29 +0000 UTC,LastTransitionTime:2022-11-11 23:59:53 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-12 00:11:29 +0000 UTC,LastTransitionTime:2022-11-11 23:59:53 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-12 00:11:29 +0000 UTC,LastTransitionTime:2022-11-12 00:00:43 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-ghmn83-control-plane-cfthd,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:6a34c87f420648ed89286357bac5e05f,SystemUUID:f5f81a87-7d4f-4449-9a5a-a46b0838476d,BootID:bc964dda-66fa-47e4-a96a-66339c4471fa,KernelVersion:5.4.0-1091-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.26.0-beta.0.59+0997f9c364c4bc,KubeProxyVersion:v1.26.0-beta.0.59+0997f9c364c4bc,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:22d41031c105347b969877c2a8a9c0b78342e1d154292142dc30973ff3c2bff5 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.26.0-beta.0.30_e4d46148de9d83],SizeBytes:35103760,},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:9080dedd984175735d5f47f73bc55fc6b21d3dd647a3c69e9553bbfcdecba616 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.26.0-beta.0.30_e4d46148de9d83],SizeBytes:32082500,},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:[capzci.azurecr.io/kube-proxy@sha256:13eac570e67af041512b0ab8bd1392c03ead6d26afb5a9ce331d2e57e54b72e0 capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.59_0997f9c364c4bc],SizeBytes:21532932,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:b8be047c8555a8b6be704cacdf69a22cd5cc56e87b3a46593eb40cf00d0cbd87 gcr.io/k8s-staging-ci-images/kube-proxy:v1.26.0-beta.0.30_e4d46148de9d83],SizeBytes:21418976,},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:cdd11b6425ed55fc911da61eb3429dade38ce72ff70f7a31f4969454403dc1b5 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.26.0-beta.0.30_e4d46148de9d83],SizeBytes:17336935,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:f478aa916568b00269068ff1e9ff742ecc16192eb6e371e30f69f75df904162e registry.k8s.io/kube-scheduler:v1.25.3],SizeBytes:15798744,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Nov 12 00:14:20.437: INFO:
Logging kubelet events for node capz-conf-ghmn83-control-plane-cfthd
Nov 12 00:14:20.636: INFO:
Logging pods the kubelet thinks is on node capz-conf-ghmn83-control-plane-cfthd
Nov 12 00:14:20.869: INFO: kube-proxy-xvfvk started at 2022-11-12 00:00:23 +0000 UTC (0+1 container statuses recorded)
Nov 12 00:14:20.869: INFO: Container kube-proxy ready: true, restart count 0
Nov 12 00:14:20.869: INFO: coredns-64475449fc-stlx5 started at 2022-11-12 00:00:44 +0000 UTC (0+1 container statuses recorded)
Nov 12 00:14:20.869: INFO: Container coredns ready: true, restart count 0
Nov 12 00:14:20.869: INFO: kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd started at <nil> (0+0 container statuses recorded)
Nov 12 00:14:20.869: INFO: kube-apiserver-capz-conf-ghmn83-control-plane-cfthd started at <nil> (0+0 container statuses recorded)
Nov 12 00:14:20.869: INFO: kube-scheduler-capz-conf-ghmn83-control-plane-cfthd started at <nil> (0+0 container statuses recorded)
Nov 12 00:14:20.869: INFO: calico-node-dk2fv started at 2022-11-12 00:00:26 +0000 UTC (2+1 container statuses recorded)
Nov 12 00:14:20.869: INFO: Init container upgrade-ipam ready: true, restart count 0
Nov 12 00:14:20.869: INFO: Init container install-cni ready: true, restart count 0
Nov 12 00:14:20.869: INFO: Container calico-node ready: true, restart count 0
Nov 12 00:14:20.869: INFO: coredns-64475449fc-zvt7m started at 2022-11-12 00:00:44 +0000 UTC (0+1 container statuses recorded)
Nov 12 00:14:20.869: INFO: Container coredns ready: true, restart count 0
Nov 12 00:14:20.869: INFO: metrics-server-954b56d74-gzfdm started at 2022-11-12 00:00:44 +0000 UTC (0+1 container statuses recorded)
Nov 12 00:14:20.869: INFO: Container metrics-server ready: true, restart count 0
Nov 12 00:14:20.869: INFO: calico-kube-controllers-56c5ff4bf8-2mrcx started at 2022-11-12 00:00:44 +0000 UTC (0+1 container statuses recorded)
Nov 12 00:14:20.869: INFO: Container calico-kube-controllers ready: true, restart count 0
Nov 12 00:14:20.869: INFO: etcd-capz-conf-ghmn83-control-plane-cfthd started at 2022-11-11 23:59:53 +0000 UTC (0+1 container statuses recorded)
Nov 12 00:14:20.869: INFO: Container etcd ready: true, restart count 0
Nov 12 00:14:21.488: INFO:
Latency metrics for node capz-conf-ghmn83-control-plane-cfthd
Nov 12 00:14:21.488: INFO:
Logging node info for node capz-conf-ld5bg
Nov 12 00:14:21.633: INFO: Node Info: &Node{ObjectMeta:{capz-conf-ld5bg 8b47b69b-d14e-4713-987b-5bf63f657fc3 1588 0 2022-11-12 00:03:10 +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-ld5bg 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-ghmn83 cluster.x-k8s.io/cluster-namespace:capz-conf-ghmn83 cluster.x-k8s.io/machine:capz-conf-ghmn83-md-win-66545b4fbb-vlb4j cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-ghmn83-md-win-66545b4fbb 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.249.65 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:8e:28:53 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-12 00:03:10 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-12 00:03:10 +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-12 00:03:36 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-12 00:03:59 +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-12 00:04:23 +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-12 00:09:16 +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-ghmn83/providers/Microsoft.Compute/virtualMachines/capz-conf-ld5bg,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-12 00:09:16 +0000 UTC,LastTransitionTime:2022-11-12 00:03:10 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-12 00:09:16 +0000 UTC,LastTransitionTime:2022-11-12 00:03:10 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-12 00:09:16 +0000 UTC,LastTransitionTime:2022-11-12 00:03:10 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-12 00:09:16 +0000 UTC,LastTransitionTime:2022-11-12 00:03:36 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-ld5bg,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-ld5bg,SystemUUID:C7FE8C04-2BE1-418C-97F4-77EAAB30670C,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.26.0-beta.0.59+0997f9c364c4bc-dirty,KubeProxyVersion:v1.26.0-beta.0.59+0997f9c364c4bc-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.26.0-beta.0.30_e4d46148de9d83-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 12 00:14:21.633: INFO:
Logging kubelet events for node capz-conf-ld5bg
Nov 12 00:14:21.833: INFO:
Logging pods the kubelet thinks is on node capz-conf-ld5bg
Nov 12 00:14:22.041: INFO: kube-proxy-windows-lrqbz started at 2022-11-12 00:03:10 +0000 UTC (0+1 container statuses recorded)
Nov 12 00:14:22.041: INFO: Container kube-proxy ready: true, restart count 0
Nov 12 00:14:22.041: INFO: calico-node-windows-wtrbt started at 2022-11-12 00:03:10 +0000 UTC (1+2 container statuses recorded)
Nov 12 00:14:22.041: INFO: Init container install-cni ready: true, restart count 0
Nov 12 00:14:22.041: INFO: Container calico-node-felix ready: true, restart count 1
Nov 12 00:14:22.041: INFO: Container calico-node-startup ready: true, restart count 0
Nov 12 00:14:22.041: INFO: containerd-logger-vhvkr started at 2022-11-12 00:03:10 +0000 UTC (0+1 container statuses recorded)
Nov 12 00:14:22.041: INFO: Container containerd-logger ready: true, restart count 0
Nov 12 00:14:22.041: INFO: csi-proxy-hq2bc started at 2022-11-12 00:03:36 +0000 UTC (0+1 container statuses recorded)
Nov 12 00:14:22.041: INFO: Container csi-proxy ready: true, restart count 0
Nov 12 00:14:22.704: INFO:
Latency metrics for node capz-conf-ld5bg
Nov 12 00:14:22.845: INFO: Running kubectl logs on non-ready containers in kube-system
Nov 12 00:14:23.234: INFO: Failed to get logs of pod kube-apiserver-capz-conf-ghmn83-control-plane-cfthd, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-ghmn83-control-plane-cfthd)
Nov 12 00:14:23.234: INFO: Logs of kube-system/kube-apiserver-capz-conf-ghmn83-control-plane-cfthd:kube-apiserver on node capz-conf-ghmn83-control-plane-cfthd
Nov 12 00:14:23.234: INFO: : STARTLOG
ENDLOG for container kube-system:kube-apiserver-capz-conf-ghmn83-control-plane-cfthd:kube-apiserver
Nov 12 00:14:23.634: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd)
Nov 12 00:14:23.634: INFO: Logs of kube-system/kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd:kube-controller-manager on node capz-conf-ghmn83-control-plane-cfthd
Nov 12 00:14:23.634: INFO: : STARTLOG
ENDLOG for container kube-system:kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd:kube-controller-manager
Nov 12 00:14:24.035: INFO: Failed to get logs of pod kube-scheduler-capz-conf-ghmn83-control-plane-cfthd, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-ghmn83-control-plane-cfthd)
Nov 12 00:14:24.035: INFO: Logs of kube-system/kube-scheduler-capz-conf-ghmn83-control-plane-cfthd:kube-scheduler on node capz-conf-ghmn83-control-plane-cfthd
Nov 12 00:14:24.035: INFO: : STARTLOG
ENDLOG for container kube-system:kube-scheduler-capz-conf-ghmn83-control-plane-cfthd:kube-scheduler
Nov 12 00:14:24.035: 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-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
kube-controller-manager-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd Pending []
kube-scheduler-capz-conf-ghmn83-control-plane-cfthd capz-conf-ghmn83-control-plane-cfthd 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({0x669fa20?, 0x788a1b8?, 0x0?}, {0x75ac416, 0x4}, {0xc0000b9f20, 0x0, 0x0?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x669fa20?, 0x788a1b8?, 0x0?}, {0xc0000b9f20?, 0x0?, 0x0?})
/usr/local/go/src/reflect/value.go:368 +0xbc
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
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]