PR #114157 pull-kubernetes-e2e-capz-windows-containerd #1597056471260991488
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | Octopusjust: pkg/volume/azuredd: Fix test order in attacher_test.go |
| Result | SUCCESS |
| Tests | 4 failed / 6 succeeded |
| Started | |
| Elapsed | 1h5m |
| Revision | 89e893fc79fc5ec0ec3c7b9e81e11eeacf3fede6 |
| Refs |
114157 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:249
k8s.io/kubernetes/test/e2e.setupSuite()
test/e2e/e2e.go:249 +0x4de
k8s.io/kubernetes/test/e2e.glob..func1()
test/e2e/e2e.go:81 +0x8f
reflect.Value.call({0x66a9bc0?, 0x78952d0?, 0x0?}, {0x75b6e72, 0x4}, {0xc0000b4f20, 0x0, 0x0?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x66a9bc0?, 0x78952d0?, 0x0?}, {0xc0000b4f20?, 0x0?, 0x0?})
/usr/local/go/src/reflect/value.go:368 +0xbc
[SynchronizedBeforeSuite] TOP-LEVEL
test/e2e/e2e.go:77
Nov 28 03:20:02.558: INFO: >>> kubeConfig: /tmp/kubeconfig
Nov 28 03:20:02.561: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Nov 28 03:20:02.853: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Nov 28 03:20:03.053: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:03.053: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:03.053: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:03.053: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Nov 28 03:20:03.053: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:03.053: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:03.053: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:03.053: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:03.053: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:03.053: INFO:
Nov 28 03:20:05.248: INFO: The status of Pod calico-node-windows-7r7ct is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:05.248: INFO: The status of Pod calico-node-windows-rqt9z is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:05.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:05.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:05.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:05.248: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Nov 28 03:20:05.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:05.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:05.248: INFO: calico-node-windows-7r7ct capz-conf-688fs Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:09 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:39 +0000 UTC }]
Nov 28 03:20:05.248: INFO: calico-node-windows-rqt9z capz-conf-m57zl Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:08 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:36 +0000 UTC }]
Nov 28 03:20:05.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:05.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:05.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:05.248: INFO:
Nov 28 03:20:07.249: INFO: The status of Pod calico-node-windows-7r7ct is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:07.249: INFO: The status of Pod calico-node-windows-rqt9z is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:07.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:07.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:07.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:07.249: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Nov 28 03:20:07.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:07.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:07.249: INFO: calico-node-windows-7r7ct capz-conf-688fs Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:09 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:39 +0000 UTC }]
Nov 28 03:20:07.249: INFO: calico-node-windows-rqt9z capz-conf-m57zl Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:08 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:36 +0000 UTC }]
Nov 28 03:20:07.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:07.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:07.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:07.249: INFO:
Nov 28 03:20:09.248: INFO: The status of Pod calico-node-windows-7r7ct is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:09.248: INFO: The status of Pod calico-node-windows-rqt9z is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:09.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:09.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:09.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:09.248: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Nov 28 03:20:09.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:09.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:09.248: INFO: calico-node-windows-7r7ct capz-conf-688fs Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:09 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:39 +0000 UTC }]
Nov 28 03:20:09.248: INFO: calico-node-windows-rqt9z capz-conf-m57zl Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:08 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:36 +0000 UTC }]
Nov 28 03:20:09.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:09.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:09.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:09.248: INFO:
Nov 28 03:20:11.254: INFO: The status of Pod calico-node-windows-7r7ct is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:11.254: INFO: The status of Pod calico-node-windows-rqt9z is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:11.254: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:11.254: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:11.254: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:11.254: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Nov 28 03:20:11.254: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:11.254: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:11.254: INFO: calico-node-windows-7r7ct capz-conf-688fs Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:09 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:39 +0000 UTC }]
Nov 28 03:20:11.254: INFO: calico-node-windows-rqt9z capz-conf-m57zl Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:08 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:36 +0000 UTC }]
Nov 28 03:20:11.254: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:11.254: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:11.254: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:11.254: INFO:
Nov 28 03:20:13.250: INFO: The status of Pod calico-node-windows-rqt9z is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:13.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:13.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:13.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:13.250: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Nov 28 03:20:13.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:13.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:13.250: INFO: calico-node-windows-rqt9z capz-conf-m57zl Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:08 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:04 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:36 +0000 UTC }]
Nov 28 03:20:13.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:13.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:13.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:13.250: INFO:
Nov 28 03:20:15.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:15.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:15.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:15.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Nov 28 03:20:15.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:15.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:15.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:15.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:15.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:15.248: INFO:
Nov 28 03:20:17.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:17.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:17.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:17.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Nov 28 03:20:17.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:17.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:17.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:17.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:17.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:17.250: INFO:
Nov 28 03:20:19.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:19.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:19.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:19.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Nov 28 03:20:19.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:19.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:19.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:19.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:19.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:19.247: INFO:
Nov 28 03:20:21.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:21.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:21.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:21.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Nov 28 03:20:21.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:21.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:21.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:21.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:21.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:21.248: INFO:
Nov 28 03:20:23.255: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:23.255: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:23.255: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:23.255: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Nov 28 03:20:23.255: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:23.255: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:23.255: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:23.255: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:23.255: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:23.255: INFO:
Nov 28 03:20:25.251: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:25.251: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:25.251: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:25.251: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Nov 28 03:20:25.251: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:25.251: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:25.251: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:25.251: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:25.251: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:25.251: INFO:
Nov 28 03:20:27.257: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:27.257: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:27.257: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:27.257: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Nov 28 03:20:27.257: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:27.257: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:27.257: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:27.257: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:27.257: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:27.257: INFO:
Nov 28 03:20:29.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:29.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:29.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:29.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Nov 28 03:20:29.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:29.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:29.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:29.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:29.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:29.249: INFO:
Nov 28 03:20:31.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:31.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:31.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:31.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Nov 28 03:20:31.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:31.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:31.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:31.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:31.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:31.249: INFO:
Nov 28 03:20:33.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:33.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:33.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:33.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
Nov 28 03:20:33.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:33.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:33.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:33.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:33.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:33.248: INFO:
Nov 28 03:20:35.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:35.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:35.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:35.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
Nov 28 03:20:35.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:35.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:35.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:35.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:35.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:35.247: INFO:
Nov 28 03:20:37.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:37.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:37.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:37.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
Nov 28 03:20:37.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:37.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:37.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:37.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:37.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:37.248: INFO:
Nov 28 03:20:39.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:39.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:39.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:39.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
Nov 28 03:20:39.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:39.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:39.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:39.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:39.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:39.248: INFO:
Nov 28 03:20:41.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:41.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:41.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:41.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
Nov 28 03:20:41.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:41.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:41.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:41.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:41.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:41.249: INFO:
Nov 28 03:20:43.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:43.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:43.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:43.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
Nov 28 03:20:43.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:43.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:43.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:43.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:43.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:43.249: INFO:
Nov 28 03:20:45.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:45.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:45.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:45.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
Nov 28 03:20:45.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:45.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:45.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:45.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:45.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:45.247: INFO:
Nov 28 03:20:47.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:47.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:47.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:47.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
Nov 28 03:20:47.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:47.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:47.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:47.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:47.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:47.250: INFO:
Nov 28 03:20:49.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:49.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:49.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:49.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
Nov 28 03:20:49.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:49.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:49.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:49.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:49.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:49.249: INFO:
Nov 28 03:20:51.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:51.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:51.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:51.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
Nov 28 03:20:51.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:51.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:51.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:51.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:51.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:51.250: INFO:
Nov 28 03:20:53.251: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:53.251: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:53.251: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:53.251: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
Nov 28 03:20:53.251: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:53.251: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:53.251: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:53.251: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:53.251: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:53.251: INFO:
Nov 28 03:20:55.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:55.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:55.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:55.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
Nov 28 03:20:55.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:55.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:55.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:55.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:55.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:55.250: INFO:
Nov 28 03:20:57.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:57.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:57.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:57.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
Nov 28 03:20:57.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:57.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:57.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:57.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:57.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:57.249: INFO:
Nov 28 03:20:59.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:59.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:59.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:20:59.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
Nov 28 03:20:59.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:20:59.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:20:59.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:59.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:59.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:20:59.248: INFO:
Nov 28 03:21:01.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:01.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:01.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:01.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
Nov 28 03:21:01.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:01.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:01.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:01.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:01.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:01.249: INFO:
Nov 28 03:21:03.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:03.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:03.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:03.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
Nov 28 03:21:03.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:03.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:03.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:03.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:03.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:03.249: INFO:
Nov 28 03:21:05.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:05.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:05.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:05.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
Nov 28 03:21:05.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:05.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:05.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:05.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:05.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:05.248: INFO:
Nov 28 03:21:07.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:07.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:07.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:07.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
Nov 28 03:21:07.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:07.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:07.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:07.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:07.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:07.249: INFO:
Nov 28 03:21:09.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:09.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:09.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:09.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
Nov 28 03:21:09.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:09.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:09.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:09.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:09.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:09.247: INFO:
Nov 28 03:21:11.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:11.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:11.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:11.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
Nov 28 03:21:11.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:11.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:11.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:11.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:11.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:11.248: INFO:
Nov 28 03:21:13.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:13.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:13.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:13.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
Nov 28 03:21:13.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:13.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:13.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:13.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:13.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:13.247: INFO:
Nov 28 03:21:15.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:15.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:15.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:15.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
Nov 28 03:21:15.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:15.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:15.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:15.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:15.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:15.248: INFO:
Nov 28 03:21:17.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:17.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:17.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:17.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
Nov 28 03:21:17.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:17.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:17.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:17.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:17.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:17.249: INFO:
Nov 28 03:21:19.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:19.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:19.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:19.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
Nov 28 03:21:19.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:19.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:19.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:19.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:19.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:19.247: INFO:
Nov 28 03:21:21.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:21.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:21.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:21.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
Nov 28 03:21:21.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:21.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:21.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:21.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:21.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:21.250: INFO:
Nov 28 03:21:23.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:23.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:23.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:23.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
Nov 28 03:21:23.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:23.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:23.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:23.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:23.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:23.247: INFO:
Nov 28 03:21:25.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:25.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:25.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:25.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
Nov 28 03:21:25.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:25.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:25.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:25.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:25.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:25.248: INFO:
Nov 28 03:21:27.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:27.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:27.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:27.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
Nov 28 03:21:27.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:27.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:27.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:27.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:27.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:27.250: INFO:
Nov 28 03:21:29.434: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:29.434: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:29.434: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:29.434: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
Nov 28 03:21:29.434: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:29.434: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:29.434: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:29.434: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:29.434: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:29.434: INFO:
Nov 28 03:21:31.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:31.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:31.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:31.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
Nov 28 03:21:31.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:31.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:31.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:31.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:31.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:31.248: INFO:
Nov 28 03:21:33.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:33.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:33.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:33.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
Nov 28 03:21:33.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:33.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:33.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:33.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:33.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:33.247: INFO:
Nov 28 03:21:35.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:35.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:35.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:35.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
Nov 28 03:21:35.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:35.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:35.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:35.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:35.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:35.248: INFO:
Nov 28 03:21:37.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:37.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:37.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:37.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
Nov 28 03:21:37.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:37.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:37.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:37.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:37.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:37.250: INFO:
Nov 28 03:21:39.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:39.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:39.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:39.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
Nov 28 03:21:39.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:39.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:39.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:39.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:39.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:39.249: INFO:
Nov 28 03:21:41.246: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:41.246: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:41.246: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:41.246: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
Nov 28 03:21:41.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:41.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:41.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:41.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:41.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:41.247: INFO:
Nov 28 03:21:43.251: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:43.251: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:43.251: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:43.251: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
Nov 28 03:21:43.251: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:43.251: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:43.251: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:43.251: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:43.251: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:43.251: INFO:
Nov 28 03:21:45.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:45.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:45.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:45.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
Nov 28 03:21:45.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:45.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:45.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:45.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:45.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:45.247: INFO:
Nov 28 03:21:47.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:47.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:47.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:47.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
Nov 28 03:21:47.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:47.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:47.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:47.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:47.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:47.249: INFO:
Nov 28 03:21:49.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:49.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:49.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:49.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
Nov 28 03:21:49.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:49.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:49.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:49.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:49.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:49.247: INFO:
Nov 28 03:21:51.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:51.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:51.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:51.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
Nov 28 03:21:51.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:51.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:51.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:51.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:51.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:51.249: INFO:
Nov 28 03:21:53.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:53.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:53.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:53.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
Nov 28 03:21:53.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:53.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:53.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:53.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:53.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:53.249: INFO:
Nov 28 03:21:55.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:55.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:55.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:55.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
Nov 28 03:21:55.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:55.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:55.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:55.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:55.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:55.250: INFO:
Nov 28 03:21:57.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:57.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:57.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:57.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
Nov 28 03:21:57.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:57.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:57.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:57.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:57.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:57.250: INFO:
Nov 28 03:21:59.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:59.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:59.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:21:59.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
Nov 28 03:21:59.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:21:59.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:21:59.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:59.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:59.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:21:59.248: INFO:
Nov 28 03:22:01.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:01.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:01.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:01.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
Nov 28 03:22:01.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:01.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:01.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:01.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:01.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:01.247: INFO:
Nov 28 03:22:03.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:03.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:03.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:03.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
Nov 28 03:22:03.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:03.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:03.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:03.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:03.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:03.250: INFO:
Nov 28 03:22:05.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:05.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:05.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:05.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
Nov 28 03:22:05.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:05.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:05.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:05.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:05.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:05.249: INFO:
Nov 28 03:22:07.252: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:07.252: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:07.252: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:07.252: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
Nov 28 03:22:07.252: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:07.252: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:07.252: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:07.252: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:07.252: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:07.252: INFO:
Nov 28 03:22:09.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:09.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:09.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:09.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
Nov 28 03:22:09.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:09.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:09.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:09.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:09.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:09.250: INFO:
Nov 28 03:22:11.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:11.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:11.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:11.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
Nov 28 03:22:11.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:11.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:11.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:11.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:11.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:11.248: INFO:
Nov 28 03:22:13.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:13.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:13.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:13.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
Nov 28 03:22:13.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:13.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:13.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:13.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:13.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:13.249: INFO:
Nov 28 03:22:15.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:15.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:15.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:15.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
Nov 28 03:22:15.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:15.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:15.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:15.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:15.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:15.247: INFO:
Nov 28 03:22:17.252: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:17.252: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:17.252: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:17.252: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
Nov 28 03:22:17.252: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:17.252: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:17.252: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:17.252: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:17.252: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:17.252: INFO:
Nov 28 03:22:19.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:19.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:19.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:19.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
Nov 28 03:22:19.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:19.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:19.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:19.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:19.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:19.247: INFO:
Nov 28 03:22:21.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:21.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:21.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:21.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
Nov 28 03:22:21.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:21.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:21.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:21.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:21.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:21.249: INFO:
Nov 28 03:22:23.433: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:23.433: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:23.433: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:23.433: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
Nov 28 03:22:23.433: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:23.433: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:23.433: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:23.433: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:23.433: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:23.433: INFO:
Nov 28 03:22:25.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:25.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:25.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:25.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
Nov 28 03:22:25.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:25.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:25.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:25.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:25.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:25.247: INFO:
Nov 28 03:22:27.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:27.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:27.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:27.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
Nov 28 03:22:27.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:27.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:27.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:27.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:27.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:27.249: INFO:
Nov 28 03:22:29.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:29.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:29.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:29.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
Nov 28 03:22:29.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:29.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:29.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:29.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:29.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:29.248: INFO:
Nov 28 03:22:31.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:31.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:31.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:31.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
Nov 28 03:22:31.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:31.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:31.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:31.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:31.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:31.247: INFO:
Nov 28 03:22:33.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:33.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:33.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:33.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
Nov 28 03:22:33.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:33.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:33.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:33.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:33.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:33.250: INFO:
Nov 28 03:22:35.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:35.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:35.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:35.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
Nov 28 03:22:35.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:35.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:35.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:35.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:35.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:35.248: INFO:
Nov 28 03:22:37.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:37.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:37.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:37.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
Nov 28 03:22:37.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:37.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:37.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:37.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:37.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:37.247: INFO:
Nov 28 03:22:39.428: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:39.428: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:39.428: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:39.428: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
Nov 28 03:22:39.428: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:39.428: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:39.428: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:39.428: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:39.428: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:39.428: INFO:
Nov 28 03:22:41.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:41.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:41.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:41.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
Nov 28 03:22:41.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:41.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:41.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:41.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:41.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:41.247: INFO:
Nov 28 03:22:43.252: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:43.252: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:43.252: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:43.252: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
Nov 28 03:22:43.252: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:43.252: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:43.252: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:43.252: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:43.252: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:43.252: INFO:
Nov 28 03:22:45.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:45.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:45.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:45.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
Nov 28 03:22:45.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:45.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:45.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:45.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:45.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:45.247: INFO:
Nov 28 03:22:47.251: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:47.251: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:47.251: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:47.251: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
Nov 28 03:22:47.251: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:47.251: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:47.251: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:47.251: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:47.251: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:47.251: INFO:
Nov 28 03:22:49.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:49.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:49.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:49.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
Nov 28 03:22:49.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:49.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:49.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:49.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:49.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:49.248: INFO:
Nov 28 03:22:51.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:51.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:51.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:51.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
Nov 28 03:22:51.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:51.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:51.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:51.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:51.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:51.248: INFO:
Nov 28 03:22:53.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:53.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:53.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:53.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
Nov 28 03:22:53.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:53.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:53.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:53.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:53.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:53.248: INFO:
Nov 28 03:22:55.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:55.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:55.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:55.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
Nov 28 03:22:55.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:55.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:55.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:55.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:55.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:55.247: INFO:
Nov 28 03:22:57.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:57.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:57.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:57.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
Nov 28 03:22:57.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:57.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:57.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:57.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:57.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:57.249: INFO:
Nov 28 03:22:59.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:59.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:59.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:22:59.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
Nov 28 03:22:59.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:22:59.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:22:59.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:59.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:59.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:22:59.248: INFO:
Nov 28 03:23:01.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:01.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:01.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:01.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
Nov 28 03:23:01.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:01.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:01.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:01.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:01.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:01.247: INFO:
Nov 28 03:23:03.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:03.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:03.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:03.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
Nov 28 03:23:03.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:03.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:03.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:03.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:03.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:03.247: INFO:
Nov 28 03:23:05.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:05.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:05.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:05.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
Nov 28 03:23:05.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:05.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:05.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:05.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:05.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:05.249: INFO:
Nov 28 03:23:07.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:07.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:07.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:07.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
Nov 28 03:23:07.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:07.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:07.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:07.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:07.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:07.248: INFO:
Nov 28 03:23:09.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:09.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:09.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:09.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
Nov 28 03:23:09.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:09.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:09.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:09.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:09.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:09.247: INFO:
Nov 28 03:23:11.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:11.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:11.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:11.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
Nov 28 03:23:11.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:11.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:11.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:11.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:11.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:11.247: INFO:
Nov 28 03:23:13.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:13.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:13.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:13.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
Nov 28 03:23:13.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:13.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:13.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:13.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:13.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:13.247: INFO:
Nov 28 03:23:15.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:15.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:15.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:15.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
Nov 28 03:23:15.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:15.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:15.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:15.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:15.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:15.248: INFO:
Nov 28 03:23:17.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:17.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:17.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:17.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
Nov 28 03:23:17.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:17.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:17.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:17.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:17.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:17.248: INFO:
Nov 28 03:23:19.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:19.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:19.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:19.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
Nov 28 03:23:19.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:19.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:19.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:19.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:19.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:19.247: INFO:
Nov 28 03:23:21.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:21.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:21.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:21.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
Nov 28 03:23:21.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:21.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:21.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:21.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:21.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:21.248: INFO:
Nov 28 03:23:23.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:23.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:23.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:23.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
Nov 28 03:23:23.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:23.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:23.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:23.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:23.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:23.247: INFO:
Nov 28 03:23:25.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:25.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:25.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:25.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
Nov 28 03:23:25.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:25.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:25.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:25.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:25.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:25.248: INFO:
Nov 28 03:23:27.260: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:27.260: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:27.260: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:27.260: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
Nov 28 03:23:27.260: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:27.260: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:27.260: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:27.260: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:27.260: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:27.260: INFO:
Nov 28 03:23:29.428: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:29.428: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:29.428: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:29.428: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
Nov 28 03:23:29.428: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:29.428: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:29.428: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:29.428: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:29.428: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:29.428: INFO:
Nov 28 03:23:31.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:31.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:31.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:31.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
Nov 28 03:23:31.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:31.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:31.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:31.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:31.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:31.247: INFO:
Nov 28 03:23:33.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:33.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:33.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:33.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
Nov 28 03:23:33.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:33.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:33.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:33.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:33.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:33.248: INFO:
Nov 28 03:23:35.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:35.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:35.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:35.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
Nov 28 03:23:35.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:35.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:35.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:35.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:35.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:35.248: INFO:
Nov 28 03:23:37.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:37.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:37.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:37.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
Nov 28 03:23:37.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:37.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:37.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:37.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:37.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:37.248: INFO:
Nov 28 03:23:39.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:39.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:39.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:39.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
Nov 28 03:23:39.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:39.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:39.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:39.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:39.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:39.247: INFO:
Nov 28 03:23:41.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:41.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:41.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:41.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
Nov 28 03:23:41.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:41.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:41.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:41.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:41.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:41.249: INFO:
Nov 28 03:23:43.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:43.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:43.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:43.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
Nov 28 03:23:43.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:43.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:43.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:43.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:43.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:43.248: INFO:
Nov 28 03:23:45.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:45.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:45.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:45.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
Nov 28 03:23:45.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:45.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:45.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:45.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:45.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:45.247: INFO:
Nov 28 03:23:47.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:47.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:47.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:47.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
Nov 28 03:23:47.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:47.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:47.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:47.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:47.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:47.248: INFO:
Nov 28 03:23:49.246: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:49.246: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:49.246: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:49.246: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
Nov 28 03:23:49.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:49.246: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:49.246: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:49.246: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:49.246: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:49.246: INFO:
Nov 28 03:23:51.254: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:51.254: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:51.254: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:51.254: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
Nov 28 03:23:51.254: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:51.254: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:51.254: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:51.254: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:51.254: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:51.254: INFO:
Nov 28 03:23:53.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:53.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:53.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:53.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
Nov 28 03:23:53.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:53.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:53.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:53.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:53.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:53.247: INFO:
Nov 28 03:23:55.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:55.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:55.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:55.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
Nov 28 03:23:55.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:55.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:55.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:55.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:55.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:55.247: INFO:
Nov 28 03:23:57.252: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:57.252: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:57.252: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:57.252: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
Nov 28 03:23:57.252: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:57.252: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:57.252: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:57.252: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:57.252: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:57.252: INFO:
Nov 28 03:23:59.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:59.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:59.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:23:59.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
Nov 28 03:23:59.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:23:59.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:23:59.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:59.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:59.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:23:59.249: INFO:
Nov 28 03:24:01.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:01.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:01.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:01.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
Nov 28 03:24:01.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:01.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:01.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:01.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:01.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:01.249: INFO:
Nov 28 03:24:03.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:03.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:03.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:03.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
Nov 28 03:24:03.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:03.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:03.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:03.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:03.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:03.248: INFO:
Nov 28 03:24:05.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:05.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:05.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:05.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
Nov 28 03:24:05.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:05.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:05.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:05.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:05.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:05.247: INFO:
Nov 28 03:24:07.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:07.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:07.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:07.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
Nov 28 03:24:07.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:07.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:07.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:07.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:07.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:07.248: INFO:
Nov 28 03:24:09.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:09.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:09.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:09.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
Nov 28 03:24:09.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:09.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:09.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:09.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:09.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:09.247: INFO:
Nov 28 03:24:11.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:11.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:11.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:11.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
Nov 28 03:24:11.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:11.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:11.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:11.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:11.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:11.249: INFO:
Nov 28 03:24:13.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:13.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:13.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:13.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
Nov 28 03:24:13.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:13.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:13.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:13.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:13.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:13.247: INFO:
Nov 28 03:24:15.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:15.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:15.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:15.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
Nov 28 03:24:15.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:15.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:15.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:15.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:15.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:15.248: INFO:
Nov 28 03:24:17.259: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:17.259: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:17.259: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:17.259: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
Nov 28 03:24:17.259: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:17.259: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:17.259: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:17.259: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:17.259: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:17.259: INFO:
Nov 28 03:24:19.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:19.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:19.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:19.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
Nov 28 03:24:19.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:19.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:19.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:19.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:19.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:19.249: INFO:
Nov 28 03:24:21.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:21.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:21.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:21.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
Nov 28 03:24:21.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:21.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:21.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:21.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:21.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:21.249: INFO:
Nov 28 03:24:23.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:23.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:23.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:23.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
Nov 28 03:24:23.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:23.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:23.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:23.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:23.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:23.249: INFO:
Nov 28 03:24:25.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:25.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:25.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:25.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
Nov 28 03:24:25.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:25.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:25.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:25.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:25.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:25.247: INFO:
Nov 28 03:24:27.251: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:27.251: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:27.251: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:27.251: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
Nov 28 03:24:27.251: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:27.251: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:27.251: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:27.251: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:27.251: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:27.251: INFO:
Nov 28 03:24:29.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:29.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:29.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:29.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
Nov 28 03:24:29.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:29.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:29.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:29.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:29.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:29.248: INFO:
Nov 28 03:24:31.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:31.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:31.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:31.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
Nov 28 03:24:31.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:31.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:31.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:31.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:31.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:31.248: INFO:
Nov 28 03:24:33.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:33.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:33.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:33.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
Nov 28 03:24:33.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:33.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:33.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:33.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:33.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:33.247: INFO:
Nov 28 03:24:35.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:35.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:35.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:35.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
Nov 28 03:24:35.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:35.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:35.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:35.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:35.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:35.247: INFO:
Nov 28 03:24:37.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:37.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:37.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:37.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
Nov 28 03:24:37.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:37.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:37.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:37.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:37.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:37.248: INFO:
Nov 28 03:24:39.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:39.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:39.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:39.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
Nov 28 03:24:39.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:39.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:39.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:39.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:39.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:39.247: INFO:
Nov 28 03:24:41.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:41.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:41.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:41.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
Nov 28 03:24:41.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:41.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:41.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:41.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:41.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:41.249: INFO:
Nov 28 03:24:43.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:43.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:43.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:43.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
Nov 28 03:24:43.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:43.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:43.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:43.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:43.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:43.247: INFO:
Nov 28 03:24:45.246: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:45.246: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:45.246: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:45.246: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
Nov 28 03:24:45.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:45.246: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:45.246: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:45.246: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:45.246: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:45.246: INFO:
Nov 28 03:24:47.252: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:47.252: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:47.252: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:47.252: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
Nov 28 03:24:47.252: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:47.252: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:47.252: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:47.252: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:47.252: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:47.252: INFO:
Nov 28 03:24:49.428: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:49.428: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:49.428: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:49.428: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
Nov 28 03:24:49.428: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:49.428: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:49.428: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:49.428: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:49.428: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:49.428: INFO:
Nov 28 03:24:51.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:51.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:51.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:51.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
Nov 28 03:24:51.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:51.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:51.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:51.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:51.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:51.248: INFO:
Nov 28 03:24:53.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:53.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:53.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:53.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
Nov 28 03:24:53.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:53.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:53.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:53.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:53.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:53.248: INFO:
Nov 28 03:24:55.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:55.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:55.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:55.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
Nov 28 03:24:55.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:55.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:55.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:55.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:55.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:55.247: INFO:
Nov 28 03:24:57.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:57.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:57.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:57.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
Nov 28 03:24:57.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:57.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:57.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:57.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:57.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:57.248: INFO:
Nov 28 03:24:59.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:59.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:59.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:24:59.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
Nov 28 03:24:59.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:24:59.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:24:59.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:59.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:59.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:24:59.247: INFO:
Nov 28 03:25:01.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:01.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:01.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:01.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
Nov 28 03:25:01.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:01.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:01.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:01.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:01.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:01.247: INFO:
Nov 28 03:25:03.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:03.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:03.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:03.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
Nov 28 03:25:03.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:03.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:03.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:03.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:03.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:03.248: INFO:
Nov 28 03:25:05.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:05.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:05.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:05.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
Nov 28 03:25:05.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:05.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:05.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:05.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:05.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:05.247: INFO:
Nov 28 03:25:07.261: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:07.261: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:07.261: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:07.261: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
Nov 28 03:25:07.261: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:07.261: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:07.261: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:07.261: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:07.261: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:07.261: INFO:
Nov 28 03:25:09.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:09.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:09.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:09.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
Nov 28 03:25:09.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:09.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:09.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:09.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:09.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:09.249: INFO:
Nov 28 03:25:11.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:11.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:11.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:11.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
Nov 28 03:25:11.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:11.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:11.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:11.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:11.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:11.248: INFO:
Nov 28 03:25:13.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:13.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:13.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:13.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
Nov 28 03:25:13.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:13.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:13.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:13.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:13.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:13.248: INFO:
Nov 28 03:25:15.251: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:15.251: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:15.251: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:15.252: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
Nov 28 03:25:15.252: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:15.252: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:15.252: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:15.252: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:15.252: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:15.252: INFO:
Nov 28 03:25:17.251: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:17.251: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:17.251: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:17.251: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
Nov 28 03:25:17.251: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:17.251: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:17.251: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:17.251: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:17.251: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:17.251: INFO:
Nov 28 03:25:19.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:19.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:19.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:19.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
Nov 28 03:25:19.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:19.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:19.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:19.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:19.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:19.248: INFO:
Nov 28 03:25:21.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:21.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:21.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:21.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
Nov 28 03:25:21.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:21.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:21.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:21.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:21.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:21.248: INFO:
Nov 28 03:25:23.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:23.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:23.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:23.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
Nov 28 03:25:23.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:23.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:23.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:23.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:23.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:23.247: INFO:
Nov 28 03:25:25.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:25.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:25.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:25.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
Nov 28 03:25:25.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:25.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:25.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:25.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:25.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:25.247: INFO:
Nov 28 03:25:27.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:27.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:27.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:27.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
Nov 28 03:25:27.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:27.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:27.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:27.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:27.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:27.247: INFO:
Nov 28 03:25:29.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:29.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:29.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:29.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
Nov 28 03:25:29.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:29.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:29.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:29.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:29.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:29.248: INFO:
Nov 28 03:25:31.252: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:31.252: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:31.252: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:31.252: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
Nov 28 03:25:31.252: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:31.252: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:31.252: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:31.252: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:31.252: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:31.252: INFO:
Nov 28 03:25:33.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:33.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:33.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:33.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
Nov 28 03:25:33.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:33.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:33.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:33.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:33.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:33.248: INFO:
Nov 28 03:25:35.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:35.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:35.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:35.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
Nov 28 03:25:35.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:35.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:35.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:35.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:35.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:35.248: INFO:
Nov 28 03:25:37.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:37.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:37.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:37.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
Nov 28 03:25:37.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:37.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:37.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:37.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:37.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:37.248: INFO:
Nov 28 03:25:39.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:39.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:39.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:39.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
Nov 28 03:25:39.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:39.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:39.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:39.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:39.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:39.247: INFO:
Nov 28 03:25:41.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:41.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:41.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:41.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
Nov 28 03:25:41.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:41.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:41.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:41.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:41.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:41.247: INFO:
Nov 28 03:25:43.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:43.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:43.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:43.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
Nov 28 03:25:43.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:43.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:43.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:43.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:43.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:43.248: INFO:
Nov 28 03:25:45.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:45.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:45.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:45.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
Nov 28 03:25:45.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:45.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:45.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:45.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:45.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:45.248: INFO:
Nov 28 03:25:47.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:47.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:47.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:47.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
Nov 28 03:25:47.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:47.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:47.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:47.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:47.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:47.248: INFO:
Nov 28 03:25:49.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:49.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:49.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:49.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
Nov 28 03:25:49.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:49.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:49.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:49.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:49.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:49.249: INFO:
Nov 28 03:25:51.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:51.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:51.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:51.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
Nov 28 03:25:51.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:51.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:51.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:51.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:51.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:51.250: INFO:
Nov 28 03:25:53.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:53.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:53.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:53.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
Nov 28 03:25:53.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:53.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:53.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:53.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:53.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:53.247: INFO:
Nov 28 03:25:55.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:55.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:55.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:55.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
Nov 28 03:25:55.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:55.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:55.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:55.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:55.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:55.247: INFO:
Nov 28 03:25:57.253: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:57.253: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:57.253: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:57.253: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
Nov 28 03:25:57.253: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:57.253: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:57.253: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:57.253: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:57.253: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:57.253: INFO:
Nov 28 03:25:59.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:59.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:59.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:25:59.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
Nov 28 03:25:59.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:25:59.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:25:59.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:59.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:59.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:25:59.248: INFO:
Nov 28 03:26:01.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:01.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:01.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:01.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
Nov 28 03:26:01.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:01.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:01.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:01.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:01.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:01.250: INFO:
Nov 28 03:26:03.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:03.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:03.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:03.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
Nov 28 03:26:03.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:03.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:03.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:03.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:03.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:03.248: INFO:
Nov 28 03:26:05.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:05.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:05.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:05.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
Nov 28 03:26:05.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:05.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:05.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:05.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:05.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:05.247: INFO:
Nov 28 03:26:07.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:07.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:07.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:07.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
Nov 28 03:26:07.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:07.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:07.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:07.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:07.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:07.247: INFO:
Nov 28 03:26:09.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:09.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:09.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:09.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
Nov 28 03:26:09.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:09.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:09.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:09.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:09.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:09.247: INFO:
Nov 28 03:26:11.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:11.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:11.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:11.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
Nov 28 03:26:11.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:11.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:11.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:11.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:11.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:11.247: INFO:
Nov 28 03:26:13.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:13.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:13.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:13.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
Nov 28 03:26:13.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:13.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:13.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:13.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:13.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:13.248: INFO:
Nov 28 03:26:15.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:15.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:15.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:15.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
Nov 28 03:26:15.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:15.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:15.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:15.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:15.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:15.249: INFO:
Nov 28 03:26:17.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:17.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:17.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:17.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
Nov 28 03:26:17.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:17.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:17.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:17.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:17.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:17.249: INFO:
Nov 28 03:26:19.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:19.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:19.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:19.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
Nov 28 03:26:19.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:19.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:19.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:19.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:19.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:19.248: INFO:
Nov 28 03:26:21.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:21.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:21.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:21.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
Nov 28 03:26:21.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:21.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:21.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:21.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:21.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:21.247: INFO:
Nov 28 03:26:23.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:23.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:23.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:23.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
Nov 28 03:26:23.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:23.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:23.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:23.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:23.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:23.247: INFO:
Nov 28 03:26:25.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:25.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:25.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:25.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
Nov 28 03:26:25.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:25.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:25.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:25.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:25.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:25.249: INFO:
Nov 28 03:26:27.252: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:27.252: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:27.252: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:27.252: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
Nov 28 03:26:27.252: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:27.252: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:27.252: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:27.252: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:27.252: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:27.252: INFO:
Nov 28 03:26:29.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:29.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:29.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:29.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
Nov 28 03:26:29.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:29.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:29.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:29.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:29.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:29.247: INFO:
Nov 28 03:26:31.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:31.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:31.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:31.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
Nov 28 03:26:31.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:31.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:31.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:31.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:31.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:31.249: INFO:
Nov 28 03:26:33.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:33.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:33.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:33.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
Nov 28 03:26:33.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:33.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:33.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:33.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:33.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:33.248: INFO:
Nov 28 03:26:35.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:35.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:35.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:35.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
Nov 28 03:26:35.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:35.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:35.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:35.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:35.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:35.249: INFO:
Nov 28 03:26:37.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:37.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:37.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:37.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
Nov 28 03:26:37.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:37.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:37.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:37.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:37.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:37.248: INFO:
Nov 28 03:26:39.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:39.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:39.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:39.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
Nov 28 03:26:39.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:39.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:39.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:39.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:39.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:39.247: INFO:
Nov 28 03:26:41.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:41.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:41.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:41.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
Nov 28 03:26:41.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:41.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:41.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:41.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:41.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:41.248: INFO:
Nov 28 03:26:43.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:43.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:43.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:43.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
Nov 28 03:26:43.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:43.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:43.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:43.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:43.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:43.248: INFO:
Nov 28 03:26:45.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:45.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:45.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:45.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
Nov 28 03:26:45.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:45.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:45.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:45.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:45.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:45.247: INFO:
Nov 28 03:26:47.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:47.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:47.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:47.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
Nov 28 03:26:47.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:47.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:47.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:47.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:47.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:47.248: INFO:
Nov 28 03:26:49.254: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:49.254: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:49.254: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:49.254: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
Nov 28 03:26:49.254: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:49.254: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:49.254: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:49.254: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:49.254: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:49.254: INFO:
Nov 28 03:26:51.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:51.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:51.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:51.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
Nov 28 03:26:51.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:51.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:51.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:51.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:51.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:51.249: INFO:
Nov 28 03:26:53.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:53.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:53.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:53.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
Nov 28 03:26:53.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:53.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:53.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:53.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:53.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:53.247: INFO:
Nov 28 03:26:55.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:55.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:55.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:55.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
Nov 28 03:26:55.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:55.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:55.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:55.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:55.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:55.247: INFO:
Nov 28 03:26:57.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:57.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:57.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:57.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
Nov 28 03:26:57.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:57.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:57.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:57.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:57.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:57.248: INFO:
Nov 28 03:26:59.246: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:59.246: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:59.246: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:26:59.246: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
Nov 28 03:26:59.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:26:59.246: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:26:59.246: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:59.246: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:59.246: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:26:59.246: INFO:
Nov 28 03:27:01.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:01.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:01.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:01.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
Nov 28 03:27:01.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:01.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:01.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:01.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:01.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:01.248: INFO:
Nov 28 03:27:03.246: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:03.246: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:03.246: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:03.246: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
Nov 28 03:27:03.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:03.246: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:03.246: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:03.246: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:03.246: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:03.246: INFO:
Nov 28 03:27:05.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:05.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:05.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:05.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
Nov 28 03:27:05.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:05.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:05.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:05.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:05.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:05.248: INFO:
Nov 28 03:27:07.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:07.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:07.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:07.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
Nov 28 03:27:07.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:07.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:07.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:07.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:07.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:07.249: INFO:
Nov 28 03:27:09.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:09.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:09.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:09.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
Nov 28 03:27:09.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:09.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:09.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:09.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:09.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:09.247: INFO:
Nov 28 03:27:11.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:11.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:11.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:11.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
Nov 28 03:27:11.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:11.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:11.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:11.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:11.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:11.250: INFO:
Nov 28 03:27:13.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:13.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:13.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:13.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
Nov 28 03:27:13.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:13.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:13.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:13.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:13.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:13.247: INFO:
Nov 28 03:27:15.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:15.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:15.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:15.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
Nov 28 03:27:15.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:15.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:15.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:15.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:15.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:15.247: INFO:
Nov 28 03:27:17.252: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:17.252: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:17.252: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:17.252: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
Nov 28 03:27:17.252: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:17.252: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:17.252: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:17.252: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:17.252: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:17.252: INFO:
Nov 28 03:27:19.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:19.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:19.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:19.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
Nov 28 03:27:19.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:19.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:19.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:19.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:19.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:19.248: INFO:
Nov 28 03:27:21.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:21.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:21.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:21.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
Nov 28 03:27:21.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:21.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:21.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:21.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:21.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:21.247: INFO:
Nov 28 03:27:23.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:23.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:23.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:23.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
Nov 28 03:27:23.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:23.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:23.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:23.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:23.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:23.247: INFO:
Nov 28 03:27:25.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:25.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:25.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:25.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
Nov 28 03:27:25.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:25.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:25.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:25.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:25.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:25.248: INFO:
Nov 28 03:27:27.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:27.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:27.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:27.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
Nov 28 03:27:27.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:27.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:27.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:27.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:27.251: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:27.251: INFO:
Nov 28 03:27:29.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:29.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:29.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:29.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
Nov 28 03:27:29.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:29.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:29.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:29.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:29.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:29.248: INFO:
Nov 28 03:27:31.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:31.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:31.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:31.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
Nov 28 03:27:31.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:31.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:31.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:31.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:31.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:31.250: INFO:
Nov 28 03:27:33.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:33.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:33.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:33.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
Nov 28 03:27:33.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:33.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:33.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:33.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:33.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:33.247: INFO:
Nov 28 03:27:35.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:35.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:35.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:35.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
Nov 28 03:27:35.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:35.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:35.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:35.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:35.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:35.247: INFO:
Nov 28 03:27:37.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:37.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:37.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:37.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
Nov 28 03:27:37.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:37.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:37.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:37.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:37.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:37.248: INFO:
Nov 28 03:27:39.428: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:39.429: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:39.429: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:39.429: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
Nov 28 03:27:39.429: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:39.429: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:39.429: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:39.429: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:39.429: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:39.429: INFO:
Nov 28 03:27:41.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:41.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:41.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:41.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
Nov 28 03:27:41.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:41.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:41.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:41.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:41.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:41.248: INFO:
Nov 28 03:27:43.254: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:43.254: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:43.254: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:43.254: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
Nov 28 03:27:43.254: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:43.254: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:43.254: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:43.254: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:43.254: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:43.254: INFO:
Nov 28 03:27:45.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:45.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:45.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:45.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
Nov 28 03:27:45.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:45.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:45.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:45.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:45.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:45.247: INFO:
Nov 28 03:27:47.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:47.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:47.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:47.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
Nov 28 03:27:47.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:47.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:47.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:47.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:47.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:47.248: INFO:
Nov 28 03:27:49.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:49.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:49.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:49.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
Nov 28 03:27:49.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:49.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:49.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:49.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:49.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:49.249: INFO:
Nov 28 03:27:51.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:51.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:51.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:51.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
Nov 28 03:27:51.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:51.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:51.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:51.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:51.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:51.248: INFO:
Nov 28 03:27:53.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:53.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:53.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:53.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
Nov 28 03:27:53.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:53.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:53.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:53.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:53.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:53.249: INFO:
Nov 28 03:27:55.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:55.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:55.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:55.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
Nov 28 03:27:55.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:55.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:55.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:55.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:55.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:55.249: INFO:
Nov 28 03:27:57.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:57.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:57.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:57.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
Nov 28 03:27:57.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:57.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:57.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:57.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:57.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:57.249: INFO:
Nov 28 03:27:59.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:59.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:59.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:27:59.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
Nov 28 03:27:59.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:27:59.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:27:59.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:59.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:59.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:27:59.247: INFO:
Nov 28 03:28:01.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:01.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:01.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:01.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
Nov 28 03:28:01.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:01.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:01.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:01.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:01.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:01.247: INFO:
Nov 28 03:28:03.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:03.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:03.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:03.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
Nov 28 03:28:03.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:03.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:03.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:03.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:03.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:03.248: INFO:
Nov 28 03:28:05.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:05.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:05.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:05.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
Nov 28 03:28:05.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:05.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:05.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:05.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:05.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:05.249: INFO:
Nov 28 03:28:07.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:07.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:07.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:07.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
Nov 28 03:28:07.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:07.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:07.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:07.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:07.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:07.250: INFO:
Nov 28 03:28:09.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:09.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:09.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:09.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
Nov 28 03:28:09.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:09.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:09.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:09.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:09.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:09.248: INFO:
Nov 28 03:28:11.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:11.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:11.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:11.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
Nov 28 03:28:11.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:11.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:11.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:11.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:11.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:11.248: INFO:
Nov 28 03:28:13.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:13.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:13.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:13.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
Nov 28 03:28:13.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:13.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:13.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:13.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:13.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:13.249: INFO:
Nov 28 03:28:15.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:15.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:15.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:15.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
Nov 28 03:28:15.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:15.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:15.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:15.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:15.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:15.249: INFO:
Nov 28 03:28:17.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:17.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:17.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:17.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
Nov 28 03:28:17.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:17.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:17.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:17.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:17.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:17.249: INFO:
Nov 28 03:28:19.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:19.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:19.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:19.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
Nov 28 03:28:19.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:19.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:19.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:19.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:19.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:19.248: INFO:
Nov 28 03:28:21.251: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:21.251: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:21.251: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:21.251: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
Nov 28 03:28:21.251: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:21.251: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:21.251: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:21.251: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:21.251: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:21.251: INFO:
Nov 28 03:28:23.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:23.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:23.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:23.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
Nov 28 03:28:23.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:23.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:23.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:23.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:23.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:23.248: INFO:
Nov 28 03:28:25.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:25.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:25.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:25.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
Nov 28 03:28:25.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:25.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:25.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:25.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:25.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:25.250: INFO:
Nov 28 03:28:27.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:27.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:27.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:27.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
Nov 28 03:28:27.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:27.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:27.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:27.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:27.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:27.248: INFO:
Nov 28 03:28:29.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:29.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:29.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:29.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
Nov 28 03:28:29.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:29.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:29.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:29.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:29.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:29.250: INFO:
Nov 28 03:28:31.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:31.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:31.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:31.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
Nov 28 03:28:31.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:31.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:31.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:31.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:31.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:31.249: INFO:
Nov 28 03:28:33.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:33.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:33.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:33.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
Nov 28 03:28:33.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:33.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:33.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:33.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:33.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:33.248: INFO:
Nov 28 03:28:35.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:35.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:35.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:35.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
Nov 28 03:28:35.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:35.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:35.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:35.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:35.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:35.249: INFO:
Nov 28 03:28:37.254: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:37.254: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:37.254: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:37.254: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
Nov 28 03:28:37.254: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:37.254: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:37.254: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:37.254: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:37.254: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:37.254: INFO:
Nov 28 03:28:39.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:39.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:39.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:39.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
Nov 28 03:28:39.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:39.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:39.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:39.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:39.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:39.249: INFO:
Nov 28 03:28:41.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:41.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:41.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:41.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
Nov 28 03:28:41.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:41.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:41.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:41.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:41.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:41.248: INFO:
Nov 28 03:28:43.246: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:43.246: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:43.246: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:43.246: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
Nov 28 03:28:43.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:43.246: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:43.246: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:43.246: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:43.246: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:43.246: INFO:
Nov 28 03:28:45.246: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:45.246: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:45.246: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:45.246: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
Nov 28 03:28:45.246: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:45.246: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:45.246: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:45.246: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:45.246: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:45.246: INFO:
Nov 28 03:28:47.251: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:47.251: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:47.251: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:47.251: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
Nov 28 03:28:47.251: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:47.251: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:47.251: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:47.251: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:47.251: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:47.251: INFO:
Nov 28 03:28:49.255: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:49.255: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:49.255: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:49.255: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
Nov 28 03:28:49.255: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:49.255: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:49.255: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:49.255: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:49.255: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:49.255: INFO:
Nov 28 03:28:51.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:51.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:51.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:51.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
Nov 28 03:28:51.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:51.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:51.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:51.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:51.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:51.247: INFO:
Nov 28 03:28:53.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:53.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:53.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:53.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
Nov 28 03:28:53.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:53.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:53.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:53.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:53.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:53.248: INFO:
Nov 28 03:28:55.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:55.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:55.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:55.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
Nov 28 03:28:55.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:55.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:55.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:55.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:55.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:55.247: INFO:
Nov 28 03:28:57.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:57.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:57.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:57.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
Nov 28 03:28:57.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:57.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:57.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:57.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:57.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:57.248: INFO:
Nov 28 03:28:59.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:59.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:59.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:28:59.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
Nov 28 03:28:59.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:28:59.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:28:59.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:59.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:59.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:28:59.247: INFO:
Nov 28 03:29:01.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:01.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:01.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:01.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
Nov 28 03:29:01.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:01.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:01.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:01.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:01.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:01.247: INFO:
Nov 28 03:29:03.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:03.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:03.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:03.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
Nov 28 03:29:03.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:03.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:03.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:03.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:03.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:03.249: INFO:
Nov 28 03:29:05.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:05.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:05.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:05.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
Nov 28 03:29:05.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:05.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:05.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:05.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:05.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:05.249: INFO:
Nov 28 03:29:07.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:07.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:07.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:07.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
Nov 28 03:29:07.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:07.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:07.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:07.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:07.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:07.248: INFO:
Nov 28 03:29:09.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:09.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:09.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:09.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
Nov 28 03:29:09.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:09.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:09.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:09.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:09.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:09.247: INFO:
Nov 28 03:29:11.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:11.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:11.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:11.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
Nov 28 03:29:11.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:11.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:11.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:11.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:11.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:11.248: INFO:
Nov 28 03:29:13.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:13.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:13.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:13.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
Nov 28 03:29:13.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:13.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:13.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:13.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:13.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:13.248: INFO:
Nov 28 03:29:15.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:15.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:15.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:15.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
Nov 28 03:29:15.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:15.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:15.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:15.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:15.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:15.248: INFO:
Nov 28 03:29:17.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:17.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:17.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:17.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
Nov 28 03:29:17.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:17.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:17.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:17.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:17.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:17.249: INFO:
Nov 28 03:29:19.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:19.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:19.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:19.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
Nov 28 03:29:19.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:19.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:19.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:19.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:19.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:19.248: INFO:
Nov 28 03:29:21.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:21.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:21.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:21.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
Nov 28 03:29:21.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:21.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:21.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:21.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:21.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:21.247: INFO:
Nov 28 03:29:23.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:23.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:23.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:23.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
Nov 28 03:29:23.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:23.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:23.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:23.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:23.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:23.248: INFO:
Nov 28 03:29:25.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:25.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:25.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:25.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
Nov 28 03:29:25.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:25.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:25.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:25.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:25.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:25.248: INFO:
Nov 28 03:29:27.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:27.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:27.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:27.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
Nov 28 03:29:27.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:27.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:27.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:27.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:27.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:27.249: INFO:
Nov 28 03:29:29.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:29.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:29.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:29.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
Nov 28 03:29:29.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:29.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:29.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:29.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:29.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:29.249: INFO:
Nov 28 03:29:31.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:31.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:31.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:31.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
Nov 28 03:29:31.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:31.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:31.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:31.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:31.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:31.247: INFO:
Nov 28 03:29:33.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:33.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:33.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:33.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
Nov 28 03:29:33.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:33.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:33.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:33.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:33.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:33.250: INFO:
Nov 28 03:29:35.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:35.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:35.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:35.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
Nov 28 03:29:35.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:35.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:35.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:35.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:35.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:35.247: INFO:
Nov 28 03:29:37.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:37.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:37.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:37.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
Nov 28 03:29:37.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:37.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:37.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:37.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:37.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:37.248: INFO:
Nov 28 03:29:39.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:39.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:39.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:39.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
Nov 28 03:29:39.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:39.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:39.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:39.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:39.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:39.248: INFO:
Nov 28 03:29:41.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:41.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:41.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:41.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
Nov 28 03:29:41.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:41.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:41.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:41.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:41.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:41.248: INFO:
Nov 28 03:29:43.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:43.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:43.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:43.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
Nov 28 03:29:43.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:43.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:43.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:43.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:43.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:43.249: INFO:
Nov 28 03:29:45.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:45.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:45.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:45.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
Nov 28 03:29:45.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:45.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:45.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:45.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:45.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:45.247: INFO:
Nov 28 03:29:47.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:47.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:47.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:47.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
Nov 28 03:29:47.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:47.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:47.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:47.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:47.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:47.249: INFO:
Nov 28 03:29:49.250: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:49.250: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:49.250: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:49.250: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
Nov 28 03:29:49.250: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:49.250: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:49.250: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:49.250: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:49.250: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:49.250: INFO:
Nov 28 03:29:51.248: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:51.248: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:51.248: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:51.248: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
Nov 28 03:29:51.248: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:51.248: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:51.248: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:51.248: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:51.248: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:51.248: INFO:
Nov 28 03:29:53.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:53.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:53.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:53.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
Nov 28 03:29:53.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:53.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:53.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:53.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:53.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:53.249: INFO:
Nov 28 03:29:55.249: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:55.249: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:55.249: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:55.249: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
Nov 28 03:29:55.249: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:55.249: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:55.249: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:55.249: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:55.249: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:55.249: INFO:
Nov 28 03:29:57.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:57.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:57.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:57.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
Nov 28 03:29:57.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:57.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:57.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:57.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:57.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:57.247: INFO:
Nov 28 03:29:59.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:59.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:59.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:29:59.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Nov 28 03:29:59.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:29:59.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:29:59.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:59.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:59.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:29:59.247: INFO:
Nov 28 03:30:01.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:30:01.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:30:01.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:30:01.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Nov 28 03:30:01.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:30:01.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:30:01.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:30:01.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:30:01.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:30:01.247: INFO:
Nov 28 03:30:03.247: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:30:03.247: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:30:03.247: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:30:03.247: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 28 03:30:03.247: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:30:03.247: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:30:03.247: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:30:03.247: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:30:03.247: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:30:03.247: INFO:
Nov 28 03:30:03.443: INFO: The status of Pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:30:03.443: INFO: The status of Pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:30:03.443: INFO: The status of Pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 28 03:30:03.443: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 28 03:30:03.443: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 28 03:30:03.443: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:30:03.443: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:30:03.443: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:30:03.443: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:30:03.443: INFO:
�[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m11/28/22 03:30:03.443�[0m
�[1mSTEP:�[0m Found 127 events. �[38;5;243m11/28/22 03:30:03.519�[0m
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:14:52 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-gh79ub-control-plane-rqzll_54f39ba9-d624-4628-a251-c87b75eefd98 became leader
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:14:52 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-gh79ub-control-plane-rqzll_65efc012-ff9d-4a45-8323-588eaa12d437 became leader
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:01 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-787d4945fb to 2
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:01 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-tlh99
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:01 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-gqndk
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:01 +0000 UTC - event for coredns-787d4945fb-gqndk: {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 28 03:30:03.519: INFO: At 2022-11-28 03:15:01 +0000 UTC - event for coredns-787d4945fb-tlh99: {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 28 03:30:03.519: INFO: At 2022-11-28 03:15:01 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-8b9qr
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:01 +0000 UTC - event for kube-proxy-8b9qr: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-8b9qr to capz-conf-gh79ub-control-plane-rqzll
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:02 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulDelete: Deleted pod: kube-proxy-8b9qr
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:05 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-gxd42
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:05 +0000 UTC - event for kube-proxy-gxd42: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-gxd42 to capz-conf-gh79ub-control-plane-rqzll
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:06 +0000 UTC - event for kube-proxy-gxd42: {kubelet capz-conf-gh79ub-control-plane-rqzll} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.52_c9a0e68a5a7905"
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:10 +0000 UTC - event for kube-proxy-gxd42: {kubelet capz-conf-gh79ub-control-plane-rqzll} Created: Created container kube-proxy
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:10 +0000 UTC - event for kube-proxy-gxd42: {kubelet capz-conf-gh79ub-control-plane-rqzll} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.52_c9a0e68a5a7905" in 3.801032786s (3.801037686s including waiting)
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:10 +0000 UTC - event for kube-proxy-gxd42: {kubelet capz-conf-gh79ub-control-plane-rqzll} Started: Started container kube-proxy
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:26 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:26 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-b6jt5
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:26 +0000 UTC - event for metrics-server-c9574f845-b6jt5: {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 28 03:30:03.519: INFO: At 2022-11-28 03:15:28 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:28 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-mgrj5
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:28 +0000 UTC - event for calico-kube-controllers-657b584867-mgrj5: {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 28 03:30:03.519: INFO: At 2022-11-28 03:15:28 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-xmp2d
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:28 +0000 UTC - event for calico-node-xmp2d: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-xmp2d to capz-conf-gh79ub-control-plane-rqzll
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:28 +0000 UTC - event for calico-node-xmp2d: {kubelet capz-conf-gh79ub-control-plane-rqzll} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:36 +0000 UTC - event for calico-node-xmp2d: {kubelet capz-conf-gh79ub-control-plane-rqzll} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 7.252872735s (7.252878935s including waiting)
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:36 +0000 UTC - event for calico-node-xmp2d: {kubelet capz-conf-gh79ub-control-plane-rqzll} Started: Started container upgrade-ipam
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:36 +0000 UTC - event for calico-node-xmp2d: {kubelet capz-conf-gh79ub-control-plane-rqzll} Created: Created container upgrade-ipam
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:40 +0000 UTC - event for calico-node-xmp2d: {kubelet capz-conf-gh79ub-control-plane-rqzll} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:40 +0000 UTC - event for calico-node-xmp2d: {kubelet capz-conf-gh79ub-control-plane-rqzll} Created: Created container install-cni
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:40 +0000 UTC - event for calico-node-xmp2d: {kubelet capz-conf-gh79ub-control-plane-rqzll} Started: Started container install-cni
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:42 +0000 UTC - event for calico-kube-controllers-657b584867-mgrj5: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-mgrj5 to capz-conf-gh79ub-control-plane-rqzll
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:42 +0000 UTC - event for coredns-787d4945fb-gqndk: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-gqndk to capz-conf-gh79ub-control-plane-rqzll
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:42 +0000 UTC - event for coredns-787d4945fb-tlh99: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-tlh99 to capz-conf-gh79ub-control-plane-rqzll
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:42 +0000 UTC - event for metrics-server-c9574f845-b6jt5: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-b6jt5 to capz-conf-gh79ub-control-plane-rqzll
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:43 +0000 UTC - event for calico-kube-controllers-657b584867-mgrj5: {kubelet capz-conf-gh79ub-control-plane-rqzll} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "a2e94826361093307c6b357dd3cd393d0b5db09739bd9930ca35a07367e5aa91": 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 28 03:30:03.519: INFO: At 2022-11-28 03:15:43 +0000 UTC - event for calico-node-xmp2d: {kubelet capz-conf-gh79ub-control-plane-rqzll} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:43 +0000 UTC - event for coredns-787d4945fb-gqndk: {kubelet capz-conf-gh79ub-control-plane-rqzll} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "c11c13e14e97b490c0f87c77546a261e380e01b7311391877311295c0a37644f": 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 28 03:30:03.519: INFO: At 2022-11-28 03:15:43 +0000 UTC - event for coredns-787d4945fb-tlh99: {kubelet capz-conf-gh79ub-control-plane-rqzll} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "e3e27599f4642e8a08c5981c753bc1caf49deafe2b1a807885b534ceee212e10": 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 28 03:30:03.519: INFO: At 2022-11-28 03:15:43 +0000 UTC - event for metrics-server-c9574f845-b6jt5: {kubelet capz-conf-gh79ub-control-plane-rqzll} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "dd42804aa3871c7024be7a5b97a171c622c49ed9dcc7234fd2971ccb4fc15bce": 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 28 03:30:03.519: INFO: At 2022-11-28 03:15:51 +0000 UTC - event for calico-node-xmp2d: {kubelet capz-conf-gh79ub-control-plane-rqzll} Started: Started container calico-node
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:51 +0000 UTC - event for calico-node-xmp2d: {kubelet capz-conf-gh79ub-control-plane-rqzll} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 8.353610212s (8.353631611s including waiting)
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:51 +0000 UTC - event for calico-node-xmp2d: {kubelet capz-conf-gh79ub-control-plane-rqzll} Created: Created container calico-node
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:52 +0000 UTC - event for calico-node-xmp2d: {kubelet capz-conf-gh79ub-control-plane-rqzll} 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 28 03:30:03.519: INFO: At 2022-11-28 03:15:55 +0000 UTC - event for metrics-server-c9574f845-b6jt5: {kubelet capz-conf-gh79ub-control-plane-rqzll} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:56 +0000 UTC - event for coredns-787d4945fb-tlh99: {kubelet capz-conf-gh79ub-control-plane-rqzll} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:56 +0000 UTC - event for coredns-787d4945fb-tlh99: {kubelet capz-conf-gh79ub-control-plane-rqzll} Created: Created container coredns
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:57 +0000 UTC - event for coredns-787d4945fb-tlh99: {kubelet capz-conf-gh79ub-control-plane-rqzll} Started: Started container coredns
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:57 +0000 UTC - event for coredns-787d4945fb-tlh99: {kubelet capz-conf-gh79ub-control-plane-rqzll} Unhealthy: Readiness probe failed: Get "http://192.168.126.66:8181/ready": dial tcp 192.168.126.66:8181: connect: connection refused
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:58 +0000 UTC - event for calico-kube-controllers-657b584867-mgrj5: {kubelet capz-conf-gh79ub-control-plane-rqzll} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0"
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:58 +0000 UTC - event for coredns-787d4945fb-gqndk: {kubelet capz-conf-gh79ub-control-plane-rqzll} Started: Started container coredns
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:58 +0000 UTC - event for coredns-787d4945fb-gqndk: {kubelet capz-conf-gh79ub-control-plane-rqzll} Created: Created container coredns
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:58 +0000 UTC - event for coredns-787d4945fb-gqndk: {kubelet capz-conf-gh79ub-control-plane-rqzll} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:59 +0000 UTC - event for coredns-787d4945fb-gqndk: {kubelet capz-conf-gh79ub-control-plane-rqzll} Unhealthy: Readiness probe failed: Get "http://192.168.126.67:8181/ready": dial tcp 192.168.126.67:8181: connect: connection refused
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:59 +0000 UTC - event for metrics-server-c9574f845-b6jt5: {kubelet capz-conf-gh79ub-control-plane-rqzll} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 4.311676895s (4.311825987s including waiting)
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:15:59 +0000 UTC - event for metrics-server-c9574f845-b6jt5: {kubelet capz-conf-gh79ub-control-plane-rqzll} Created: Created container metrics-server
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:16:00 +0000 UTC - event for metrics-server-c9574f845-b6jt5: {kubelet capz-conf-gh79ub-control-plane-rqzll} Started: Started container metrics-server
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:16:05 +0000 UTC - event for calico-kube-controllers-657b584867-mgrj5: {kubelet capz-conf-gh79ub-control-plane-rqzll} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 5.953377075s (7.404335074s including waiting)
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:16:05 +0000 UTC - event for calico-kube-controllers-657b584867-mgrj5: {kubelet capz-conf-gh79ub-control-plane-rqzll} Created: Created container calico-kube-controllers
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:16:06 +0000 UTC - event for calico-kube-controllers-657b584867-mgrj5: {kubelet capz-conf-gh79ub-control-plane-rqzll} Started: Started container calico-kube-controllers
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:36 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-rqt9z
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:36 +0000 UTC - event for calico-node-windows-rqt9z: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-rqt9z to capz-conf-m57zl
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:36 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-phmnj
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:36 +0000 UTC - event for containerd-logger-phmnj: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-phmnj to capz-conf-m57zl
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:36 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-jlt7l
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:36 +0000 UTC - event for kube-proxy-windows-jlt7l: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-jlt7l to capz-conf-m57zl
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:39 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-7r7ct
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:39 +0000 UTC - event for calico-node-windows-7r7ct: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-7r7ct to capz-conf-688fs
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:39 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-jz8xm
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:39 +0000 UTC - event for containerd-logger-jz8xm: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-jz8xm to capz-conf-688fs
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:39 +0000 UTC - event for containerd-logger-phmnj: {kubelet capz-conf-m57zl} FailedMount: MountVolume.SetUp failed for volume "containerd-logger-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:39 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-t2pjw
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:39 +0000 UTC - event for kube-proxy-windows-jlt7l: {kubelet capz-conf-m57zl} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:39 +0000 UTC - event for kube-proxy-windows-t2pjw: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-t2pjw to capz-conf-688fs
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:41 +0000 UTC - event for kube-proxy-windows-t2pjw: {kubelet capz-conf-688fs} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:57 +0000 UTC - event for calico-node-windows-rqt9z: {kubelet capz-conf-m57zl} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:57 +0000 UTC - event for containerd-logger-phmnj: {kubelet capz-conf-m57zl} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:57 +0000 UTC - event for kube-proxy-windows-jlt7l: {kubelet capz-conf-m57zl} Pulled: Container image "sigwindowstools/kube-proxy:v1.27.0-alpha.0.50_70617042976dc1-calico-hostprocess" already present on machine
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:58 +0000 UTC - event for calico-node-windows-7r7ct: {kubelet capz-conf-688fs} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:58 +0000 UTC - event for containerd-logger-jz8xm: {kubelet capz-conf-688fs} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:58 +0000 UTC - event for kube-proxy-windows-jlt7l: {kubelet capz-conf-m57zl} Created: Created container kube-proxy
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:58 +0000 UTC - event for kube-proxy-windows-jlt7l: {kubelet capz-conf-m57zl} Started: Started container kube-proxy
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:58 +0000 UTC - event for kube-proxy-windows-t2pjw: {kubelet capz-conf-688fs} Pulled: Container image "sigwindowstools/kube-proxy:v1.27.0-alpha.0.50_70617042976dc1-calico-hostprocess" already present on machine
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:59 +0000 UTC - event for kube-proxy-windows-t2pjw: {kubelet capz-conf-688fs} Started: Started container kube-proxy
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:18:59 +0000 UTC - event for kube-proxy-windows-t2pjw: {kubelet capz-conf-688fs} Created: Created container kube-proxy
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:02 +0000 UTC - event for calico-node-windows-rqt9z: {kubelet capz-conf-m57zl} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 5.1503035s (5.1503035s including waiting)
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:03 +0000 UTC - event for calico-node-windows-rqt9z: {kubelet capz-conf-m57zl} Created: Created container install-cni
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:03 +0000 UTC - event for calico-node-windows-rqt9z: {kubelet capz-conf-m57zl} Started: Started container install-cni
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:04 +0000 UTC - event for calico-node-windows-7r7ct: {kubelet capz-conf-688fs} Created: Created container install-cni
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:04 +0000 UTC - event for calico-node-windows-7r7ct: {kubelet capz-conf-688fs} Started: Started container install-cni
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:04 +0000 UTC - event for calico-node-windows-7r7ct: {kubelet capz-conf-688fs} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 5.0917263s (5.0919935s including waiting)
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:05 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-vpm2l
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:05 +0000 UTC - event for csi-proxy-vpm2l: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-vpm2l to capz-conf-m57zl
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:06 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-fxpht
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:06 +0000 UTC - event for csi-proxy-fxpht: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-fxpht to capz-conf-688fs
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:06 +0000 UTC - event for csi-proxy-vpm2l: {kubelet capz-conf-m57zl} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:07 +0000 UTC - event for csi-proxy-fxpht: {kubelet capz-conf-688fs} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:08 +0000 UTC - event for calico-node-windows-rqt9z: {kubelet capz-conf-m57zl} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:08 +0000 UTC - event for containerd-logger-phmnj: {kubelet capz-conf-m57zl} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 5.8903026s (10.9641145s including waiting)
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:09 +0000 UTC - event for calico-node-windows-7r7ct: {kubelet capz-conf-688fs} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:09 +0000 UTC - event for containerd-logger-jz8xm: {kubelet capz-conf-688fs} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 5.0469269s (10.1170479s including waiting)
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:18 +0000 UTC - event for containerd-logger-jz8xm: {kubelet capz-conf-688fs} Created: Created container containerd-logger
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:19 +0000 UTC - event for containerd-logger-jz8xm: {kubelet capz-conf-688fs} Started: Started container containerd-logger
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:19 +0000 UTC - event for containerd-logger-phmnj: {kubelet capz-conf-m57zl} Created: Created container containerd-logger
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:19 +0000 UTC - event for containerd-logger-phmnj: {kubelet capz-conf-m57zl} Started: Started container containerd-logger
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:29 +0000 UTC - event for csi-proxy-fxpht: {kubelet capz-conf-688fs} Started: Started container csi-proxy
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:29 +0000 UTC - event for csi-proxy-fxpht: {kubelet capz-conf-688fs} Created: Created container csi-proxy
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:29 +0000 UTC - event for csi-proxy-fxpht: {kubelet capz-conf-688fs} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 20.3060616s (22.1602687s including waiting)
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:30 +0000 UTC - event for csi-proxy-vpm2l: {kubelet capz-conf-m57zl} Started: Started container csi-proxy
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:30 +0000 UTC - event for csi-proxy-vpm2l: {kubelet capz-conf-m57zl} Created: Created container csi-proxy
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:30 +0000 UTC - event for csi-proxy-vpm2l: {kubelet capz-conf-m57zl} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 21.4161904s (23.9362441s including waiting)
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:33 +0000 UTC - event for calico-node-windows-7r7ct: {kubelet capz-conf-688fs} Created: Created container calico-node-startup
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:33 +0000 UTC - event for calico-node-windows-7r7ct: {kubelet capz-conf-688fs} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 4.3673098s (24.3759746s including waiting)
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:34 +0000 UTC - event for calico-node-windows-7r7ct: {kubelet capz-conf-688fs} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 805.4555ms (805.4555ms including waiting)
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:34 +0000 UTC - event for calico-node-windows-7r7ct: {kubelet capz-conf-688fs} Started: Started container calico-node-startup
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:34 +0000 UTC - event for calico-node-windows-7r7ct: {kubelet capz-conf-688fs} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:34 +0000 UTC - event for calico-node-windows-rqt9z: {kubelet capz-conf-m57zl} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:34 +0000 UTC - event for calico-node-windows-rqt9z: {kubelet capz-conf-m57zl} Started: Started container calico-node-startup
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:34 +0000 UTC - event for calico-node-windows-rqt9z: {kubelet capz-conf-m57zl} Created: Created container calico-node-startup
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:34 +0000 UTC - event for calico-node-windows-rqt9z: {kubelet capz-conf-m57zl} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 4.2525717s (25.8594806s including waiting)
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:35 +0000 UTC - event for calico-node-windows-rqt9z: {kubelet capz-conf-m57zl} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 782.335ms (782.335ms including waiting)
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:42 +0000 UTC - event for calico-node-windows-7r7ct: {kubelet capz-conf-688fs} Created: Created container calico-node-felix
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:42 +0000 UTC - event for calico-node-windows-7r7ct: {kubelet capz-conf-688fs} Started: Started container calico-node-felix
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:43 +0000 UTC - event for calico-node-windows-rqt9z: {kubelet capz-conf-m57zl} Created: Created container calico-node-felix
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:19:43 +0000 UTC - event for calico-node-windows-rqt9z: {kubelet capz-conf-m57zl} Started: Started container calico-node-felix
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:20:04 +0000 UTC - event for calico-node-windows-7r7ct: {kubelet capz-conf-688fs} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 689.2284ms (689.2284ms including waiting)
Nov 28 03:30:03.519: INFO: At 2022-11-28 03:20:05 +0000 UTC - event for calico-node-windows-rqt9z: {kubelet capz-conf-m57zl} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 735.8845ms (735.8845ms including waiting)
Nov 28 03:30:03.598: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 28 03:30:03.598: INFO: calico-kube-controllers-657b584867-mgrj5 capz-conf-gh79ub-control-plane-rqzll Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:42 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:16:06 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:16:06 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:42 +0000 UTC }]
Nov 28 03:30:03.598: INFO: calico-node-windows-7r7ct capz-conf-688fs Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:09 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:12 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:12 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:39 +0000 UTC }]
Nov 28 03:30:03.598: INFO: calico-node-windows-rqt9z capz-conf-m57zl Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:08 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:13 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:20:13 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:36 +0000 UTC }]
Nov 28 03:30:03.598: INFO: calico-node-xmp2d capz-conf-gh79ub-control-plane-rqzll Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:43 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:53 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:28 +0000 UTC }]
Nov 28 03:30:03.598: INFO: containerd-logger-jz8xm capz-conf-688fs Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:39 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:19 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:19 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:39 +0000 UTC }]
Nov 28 03:30:03.598: INFO: containerd-logger-phmnj capz-conf-m57zl Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:37 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:20 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:20 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:36 +0000 UTC }]
Nov 28 03:30:03.598: INFO: coredns-787d4945fb-gqndk capz-conf-gh79ub-control-plane-rqzll Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:42 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:16:03 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:16:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:42 +0000 UTC }]
Nov 28 03:30:03.598: INFO: coredns-787d4945fb-tlh99 capz-conf-gh79ub-control-plane-rqzll Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:42 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:16:03 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:16:03 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:42 +0000 UTC }]
Nov 28 03:30:03.598: INFO: csi-proxy-fxpht capz-conf-688fs Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:06 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:30 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:30 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:06 +0000 UTC }]
Nov 28 03:30:03.598: INFO: csi-proxy-vpm2l capz-conf-m57zl Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:05 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:30 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:30 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:05 +0000 UTC }]
Nov 28 03:30:03.598: INFO: etcd-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:03 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:11 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:11 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:03 +0000 UTC }]
Nov 28 03:30:03.598: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:30:03.598: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:30:03.598: INFO: kube-proxy-gxd42 capz-conf-gh79ub-control-plane-rqzll Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:05 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:11 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:11 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:05 +0000 UTC }]
Nov 28 03:30:03.598: INFO: kube-proxy-windows-jlt7l capz-conf-m57zl Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:37 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:58 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:58 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:36 +0000 UTC }]
Nov 28 03:30:03.598: INFO: kube-proxy-windows-t2pjw capz-conf-688fs Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:39 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:00 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:19:00 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:18:39 +0000 UTC }]
Nov 28 03:30:03.598: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Nov 28 03:30:03.598: INFO: metrics-server-c9574f845-b6jt5 capz-conf-gh79ub-control-plane-rqzll Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:42 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:16:23 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:16:23 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-28 03:15:42 +0000 UTC }]
Nov 28 03:30:03.598: INFO:
Nov 28 03:30:04.225: INFO:
Logging node info for node capz-conf-688fs
Nov 28 03:30:04.283: INFO: Node Info: &Node{ObjectMeta:{capz-conf-688fs e17712bd-a689-4f74-ab71-aa22057dc48a 2112 0 2022-11-28 03:18:39 +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:westus2 failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-688fs kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:westus2 topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-gh79ub cluster.x-k8s.io/cluster-namespace:capz-conf-gh79ub cluster.x-k8s.io/machine:capz-conf-gh79ub-md-win-77897cc8dd-9v66b cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-gh79ub-md-win-77897cc8dd 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.236.193 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:d2:b1:24 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-28 03:18:39 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-28 03:18:39 +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-28 03:19:06 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-28 03:19:55 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {Go-http-client Update v1 2022-11-28 03:20:00 +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-28 03:29:53 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:capacity":{"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-gh79ub/providers/Microsoft.Compute/virtualMachines/capz-conf-688fs,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-28 03:29:53 +0000 UTC,LastTransitionTime:2022-11-28 03:18:39 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-28 03:29:53 +0000 UTC,LastTransitionTime:2022-11-28 03:18:39 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-28 03:29:53 +0000 UTC,LastTransitionTime:2022-11-28 03:18:39 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-28 03:29:53 +0000 UTC,LastTransitionTime:2022-11-28 03:19:06 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-688fs,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-688fs,SystemUUID:66E61A02-99AA-421B-A994-EADC64B7FE4E,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.27.0-alpha.0.52+c9a0e68a5a7905-dirty,KubeProxyVersion:v1.27.0-alpha.0.52+c9a0e68a5a7905-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.27.0-alpha.0.50_70617042976dc1-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 28 03:30:04.284: INFO:
Logging kubelet events for node capz-conf-688fs
Nov 28 03:30:04.337: INFO:
Logging pods the kubelet thinks is on node capz-conf-688fs
Nov 28 03:30:04.534: INFO: kube-proxy-windows-t2pjw started at 2022-11-28 03:18:39 +0000 UTC (0+1 container statuses recorded)
Nov 28 03:30:04.534: INFO: Container kube-proxy ready: true, restart count 0
Nov 28 03:30:04.534: INFO: calico-node-windows-7r7ct started at 2022-11-28 03:18:39 +0000 UTC (1+2 container statuses recorded)
Nov 28 03:30:04.534: INFO: Init container install-cni ready: true, restart count 0
Nov 28 03:30:04.534: INFO: Container calico-node-felix ready: true, restart count 1
Nov 28 03:30:04.534: INFO: Container calico-node-startup ready: true, restart count 0
Nov 28 03:30:04.534: INFO: containerd-logger-jz8xm started at 2022-11-28 03:18:39 +0000 UTC (0+1 container statuses recorded)
Nov 28 03:30:04.534: INFO: Container containerd-logger ready: true, restart count 0
Nov 28 03:30:04.534: INFO: csi-proxy-fxpht started at 2022-11-28 03:19:06 +0000 UTC (0+1 container statuses recorded)
Nov 28 03:30:04.534: INFO: Container csi-proxy ready: true, restart count 0
Nov 28 03:30:05.172: INFO:
Latency metrics for node capz-conf-688fs
Nov 28 03:30:05.172: INFO:
Logging node info for node capz-conf-gh79ub-control-plane-rqzll
Nov 28 03:30:05.314: INFO: Node Info: &Node{ObjectMeta:{capz-conf-gh79ub-control-plane-rqzll 2a4162ea-ace4-4835-9eb5-93448ee56476 1827 0 2022-11-28 03:15:00 +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:westus2 failure-domain.beta.kubernetes.io/zone:westus2-3 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-gh79ub-control-plane-rqzll 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:westus2 topology.kubernetes.io/zone:westus2-3] map[cluster.x-k8s.io/cluster-name:capz-conf-gh79ub cluster.x-k8s.io/cluster-namespace:capz-conf-gh79ub cluster.x-k8s.io/machine:capz-conf-gh79ub-control-plane-snmc2 cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-gh79ub-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.126.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2022-11-28 03:15:00 +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-28 03:15:01 +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-28 03:15:24 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kube-controller-manager Update v1 2022-11-28 03:15:42 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2022-11-28 03:15:52 +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-28 03:26:45 +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-gh79ub/providers/Microsoft.Compute/virtualMachines/capz-conf-gh79ub-control-plane-rqzll,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-28 03:15:51 +0000 UTC,LastTransitionTime:2022-11-28 03:15:51 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-28 03:26:45 +0000 UTC,LastTransitionTime:2022-11-28 03:14:32 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-28 03:26:45 +0000 UTC,LastTransitionTime:2022-11-28 03:14:32 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-28 03:26:45 +0000 UTC,LastTransitionTime:2022-11-28 03:14:32 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-28 03:26:45 +0000 UTC,LastTransitionTime:2022-11-28 03:15:42 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-gh79ub-control-plane-rqzll,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:2a5c8d9e28b44ae68bda8a07133c914b,SystemUUID:5fe85d61-e17e-d643-8329-b2a400143bf0,BootID:bdd72928-f062-4158-9b6b-36474ebb0d3f,KernelVersion:5.4.0-1091-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.52+c9a0e68a5a7905,KubeProxyVersion:v1.27.0-alpha.0.52+c9a0e68a5a7905,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[docker.io/calico/cni@sha256:914823d144204288f881e49b93b6852febfe669074cd4e2a782860981615f521 docker.io/calico/cni:v3.23.0],SizeBytes:110494683,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[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:f7946d94c0af766c8d0c3aedb8a7c1c46edd8518bc6f04903d156fc658762284 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.50_70617042976dc1],SizeBytes:35317190,},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:b18ce206b92525ae873ba6f047b187472f2deca4f48e0a7d7dd12c4d691381b9 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.50_70617042976dc1],SizeBytes:32243482,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:d3a06262256f3e7578d5f77df137a8cdf58f9f498f35b5b56d116e8a7e31dc91 registry.k8s.io/kube-controller-manager:v1.25.3],SizeBytes:31261869,},ContainerImage{Names:[k8s.gcr.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 k8s.gcr.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:9b8431b6c0536ba43b9d498390bf060fbcfc0af66684067c74fcbc146c4df25b gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.50_70617042976dc1],SizeBytes:21534319,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:111b143ce69d01f9cc2246c0906e1d8d1a5357066443df8e7c7119a04b7cb55f capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.52_c9a0e68a5a7905],SizeBytes:21532477,},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:4298443b62d94c7db676a093c29e8ce3bbc08a95c1d2a9bbf7952ebdc161a979 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.50_70617042976dc1],SizeBytes:17482782,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:f478aa916568b00269068ff1e9ff742ecc16192eb6e371e30f69f75df904162e registry.k8s.io/kube-scheduler:v1.25.3],SizeBytes:15798744,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Nov 28 03:30:05.314: INFO:
Logging kubelet events for node capz-conf-gh79ub-control-plane-rqzll
Nov 28 03:30:05.507: INFO:
Logging pods the kubelet thinks is on node capz-conf-gh79ub-control-plane-rqzll
Nov 28 03:30:05.761: INFO: metrics-server-c9574f845-b6jt5 started at 2022-11-28 03:15:42 +0000 UTC (0+1 container statuses recorded)
Nov 28 03:30:05.761: INFO: Container metrics-server ready: true, restart count 0
Nov 28 03:30:05.761: INFO: calico-kube-controllers-657b584867-mgrj5 started at 2022-11-28 03:15:42 +0000 UTC (0+1 container statuses recorded)
Nov 28 03:30:05.761: INFO: Container calico-kube-controllers ready: true, restart count 0
Nov 28 03:30:05.761: INFO: coredns-787d4945fb-gqndk started at 2022-11-28 03:15:42 +0000 UTC (0+1 container statuses recorded)
Nov 28 03:30:05.761: INFO: Container coredns ready: true, restart count 0
Nov 28 03:30:05.761: INFO: coredns-787d4945fb-tlh99 started at 2022-11-28 03:15:42 +0000 UTC (0+1 container statuses recorded)
Nov 28 03:30:05.761: INFO: Container coredns ready: true, restart count 0
Nov 28 03:30:05.761: INFO: etcd-capz-conf-gh79ub-control-plane-rqzll started at 2022-11-28 03:15:03 +0000 UTC (0+1 container statuses recorded)
Nov 28 03:30:05.761: INFO: Container etcd ready: true, restart count 0
Nov 28 03:30:05.761: INFO: kube-apiserver-capz-conf-gh79ub-control-plane-rqzll started at <nil> (0+0 container statuses recorded)
Nov 28 03:30:05.761: INFO: kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll started at <nil> (0+0 container statuses recorded)
Nov 28 03:30:05.761: INFO: kube-scheduler-capz-conf-gh79ub-control-plane-rqzll started at <nil> (0+0 container statuses recorded)
Nov 28 03:30:05.761: INFO: kube-proxy-gxd42 started at 2022-11-28 03:15:05 +0000 UTC (0+1 container statuses recorded)
Nov 28 03:30:05.761: INFO: Container kube-proxy ready: true, restart count 0
Nov 28 03:30:05.761: INFO: calico-node-xmp2d started at 2022-11-28 03:15:28 +0000 UTC (2+1 container statuses recorded)
Nov 28 03:30:05.761: INFO: Init container upgrade-ipam ready: true, restart count 0
Nov 28 03:30:05.761: INFO: Init container install-cni ready: true, restart count 0
Nov 28 03:30:05.761: INFO: Container calico-node ready: true, restart count 0
Nov 28 03:30:06.352: INFO:
Latency metrics for node capz-conf-gh79ub-control-plane-rqzll
Nov 28 03:30:06.352: INFO:
Logging node info for node capz-conf-m57zl
Nov 28 03:30:06.508: INFO: Node Info: &Node{ObjectMeta:{capz-conf-m57zl 01abf5af-b070-4b46-b671-02896beaf6ac 2103 0 2022-11-28 03:18:36 +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:westus2 failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-m57zl kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:westus2 topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-gh79ub cluster.x-k8s.io/cluster-namespace:capz-conf-gh79ub cluster.x-k8s.io/machine:capz-conf-gh79ub-md-win-77897cc8dd-jh9z2 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-gh79ub-md-win-77897cc8dd 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.56.65 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:dc:1b:b3 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-28 03:18:36 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-28 03:18:36 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f: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-28 03:19:05 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-28 03:19:54 +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-28 03:20:01 +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-28 03:29:48 +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-gh79ub/providers/Microsoft.Compute/virtualMachines/capz-conf-m57zl,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-28 03:29:48 +0000 UTC,LastTransitionTime:2022-11-28 03:18:36 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-28 03:29:48 +0000 UTC,LastTransitionTime:2022-11-28 03:18:36 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-28 03:29:48 +0000 UTC,LastTransitionTime:2022-11-28 03:18:36 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-28 03:29:48 +0000 UTC,LastTransitionTime:2022-11-28 03:19:05 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-m57zl,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-m57zl,SystemUUID:0164E4F8-8DAD-4D93-8765-A781A08BC797,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.27.0-alpha.0.52+c9a0e68a5a7905-dirty,KubeProxyVersion:v1.27.0-alpha.0.52+c9a0e68a5a7905-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.27.0-alpha.0.50_70617042976dc1-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 28 03:30:06.508: INFO:
Logging kubelet events for node capz-conf-m57zl
Nov 28 03:30:06.707: INFO:
Logging pods the kubelet thinks is on node capz-conf-m57zl
Nov 28 03:30:06.918: INFO: kube-proxy-windows-jlt7l started at 2022-11-28 03:18:37 +0000 UTC (0+1 container statuses recorded)
Nov 28 03:30:06.918: INFO: Container kube-proxy ready: true, restart count 0
Nov 28 03:30:06.918: INFO: containerd-logger-phmnj started at 2022-11-28 03:18:37 +0000 UTC (0+1 container statuses recorded)
Nov 28 03:30:06.918: INFO: Container containerd-logger ready: true, restart count 0
Nov 28 03:30:06.918: INFO: calico-node-windows-rqt9z started at 2022-11-28 03:18:37 +0000 UTC (1+2 container statuses recorded)
Nov 28 03:30:06.918: INFO: Init container install-cni ready: true, restart count 0
Nov 28 03:30:06.918: INFO: Container calico-node-felix ready: true, restart count 1
Nov 28 03:30:06.918: INFO: Container calico-node-startup ready: true, restart count 0
Nov 28 03:30:06.918: INFO: csi-proxy-vpm2l started at 2022-11-28 03:19:05 +0000 UTC (0+1 container statuses recorded)
Nov 28 03:30:06.918: INFO: Container csi-proxy ready: true, restart count 0
Nov 28 03:30:07.561: INFO:
Latency metrics for node capz-conf-m57zl
Nov 28 03:30:07.720: INFO: Running kubectl logs on non-ready containers in kube-system
Nov 28 03:30:08.107: INFO: Failed to get logs of pod kube-apiserver-capz-conf-gh79ub-control-plane-rqzll, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-gh79ub-control-plane-rqzll)
Nov 28 03:30:08.107: INFO: Logs of kube-system/kube-apiserver-capz-conf-gh79ub-control-plane-rqzll:kube-apiserver on node capz-conf-gh79ub-control-plane-rqzll
Nov 28 03:30:08.107: INFO: : STARTLOG
ENDLOG for container kube-system:kube-apiserver-capz-conf-gh79ub-control-plane-rqzll:kube-apiserver
Nov 28 03:30:08.507: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll)
Nov 28 03:30:08.507: INFO: Logs of kube-system/kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll:kube-controller-manager on node capz-conf-gh79ub-control-plane-rqzll
Nov 28 03:30:08.507: INFO: : STARTLOG
ENDLOG for container kube-system:kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll:kube-controller-manager
Nov 28 03:30:08.908: INFO: Failed to get logs of pod kube-scheduler-capz-conf-gh79ub-control-plane-rqzll, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-gh79ub-control-plane-rqzll)
Nov 28 03:30:08.908: INFO: Logs of kube-system/kube-scheduler-capz-conf-gh79ub-control-plane-rqzll:kube-scheduler on node capz-conf-gh79ub-control-plane-rqzll
Nov 28 03:30:08.908: INFO: : STARTLOG
ENDLOG for container kube-system:kube-scheduler-capz-conf-gh79ub-control-plane-rqzll:kube-scheduler
Nov 28 03:30:08.908: 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-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
kube-controller-manager-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
kube-scheduler-capz-conf-gh79ub-control-plane-rqzll capz-conf-gh79ub-control-plane-rqzll Pending []
Full Stack Trace
k8s.io/kubernetes/test/e2e.setupSuite()
test/e2e/e2e.go:249 +0x4de
k8s.io/kubernetes/test/e2e.glob..func1()
test/e2e/e2e.go:81 +0x8f
reflect.Value.call({0x66a9bc0?, 0x78952d0?, 0x0?}, {0x75b6e72, 0x4}, {0xc0000b4f20, 0x0, 0x0?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x66a9bc0?, 0x78952d0?, 0x0?}, {0xc0000b4f20?, 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
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e suite report
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
capz-e2e Conformance Tests conformance-tests
capz-e2e Running the Cluster API E2E tests API Version Upgrade upgrade from v1alpha4 to v1beta1, and scale workload clusters created in v1alpha4 Should create a management cluster and then upgrade all the providers
capz-e2e Running the Cluster API E2E tests Running KCP upgrade in a HA cluster [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Running KCP upgrade in a HA cluster using scale in rollout [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Running the MachineDeployment rollout spec Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
capz-e2e Running the Cluster API E2E tests Running the quick-start spec Should create a workload cluster
capz-e2e Running the Cluster API E2E tests Running the self-hosted spec Should pivot the bootstrap cluster to a self-hosted cluster
capz-e2e Running the Cluster API E2E tests Running the workload cluster upgrade spec [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Should successfully exercise machine pools Should successfully create a cluster with machine pool machines
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger machine deployment remediation
capz-e2e Running the Cluster API E2E tests Should successfully scale out and scale in a MachineDeployment Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count
capz-e2e Running the Cluster API E2E tests Should successfully set and use node drain timeout A node should be forcefully removed if it cannot be drained in time
capz-e2e Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] with a single control plane node and 1 node
capz-e2e Workload cluster creation Creating a VMSS cluster [REQUIRED] with a single control plane node and an AzureMachinePool with 2 Linux and 2 Windows worker nodes
capz-e2e Workload cluster creation Creating a cluster that uses the external cloud provider and external azurediskcsi driver [OPTIONAL] with a 1 control plane nodes and 2 worker nodes
capz-e2e Workload cluster creation Creating a dual-stack cluster [OPTIONAL] With dual-stack worker node
capz-e2e Workload cluster creation Creating a highly available cluster [REQUIRED] With 3 control-plane nodes and 2 Linux and 2 Windows worker nodes
capz-e2e Workload cluster creation Creating a ipv6 control-plane cluster [REQUIRED] With ipv6 worker node
capz-e2e Workload cluster creation Creating a private cluster [OPTIONAL] Creates a public management cluster in a custom vnet
capz-e2e Workload cluster creation Creating an AKS cluster [EXPERIMENTAL][Managed Kubernetes] with a single control plane node and 1 node
capz-e2e Workload cluster creation Creating clusters using clusterclass [OPTIONAL] with a single control plane node, one linux worker node, and one windows worker node
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=external CCM=external AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with intree cloud provider
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=external CCM=internal AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with intree cloud provider
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=internal CCM=internal AzureDiskCSIMigration=false: upgrade to v1.23 should create volumes dynamically with intree cloud provider