PR #114078 pull-kubernetes-e2e-capz-windows-containerd #1595432659322933248
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | Karthik-K-N: Fix TestJitterWithNegativeMaxFactor flaky test |
| Result | SUCCESS |
| Tests | 4 failed / 6 succeeded |
| Started | |
| Elapsed | 1h14m |
| Revision | 7bfece99d9c76e2e6775ac043b50963abe1152dd |
| Refs |
114078 |
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 23 15:55:12.300: INFO: >>> kubeConfig: /tmp/kubeconfig
Nov 23 15:55:12.302: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Nov 23 15:55:12.776: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Nov 23 15:55:13.164: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:13.164: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:13.164: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:13.164: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Nov 23 15:55:13.164: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:13.164: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:13.164: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:13.164: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:13.164: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:13.164: INFO:
Nov 23 15:55:15.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:15.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:15.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:15.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Nov 23 15:55:15.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:15.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:15.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:15.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:15.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:15.549: INFO:
Nov 23 15:55:17.551: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:17.551: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:17.551: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:17.551: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Nov 23 15:55:17.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:17.551: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:17.551: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:17.551: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:17.551: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:17.551: INFO:
Nov 23 15:55:19.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:19.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:19.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:19.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Nov 23 15:55:19.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:19.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:19.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:19.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:19.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:19.546: INFO:
Nov 23 15:55:21.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:21.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:21.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:21.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Nov 23 15:55:21.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:21.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:21.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:21.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:21.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:21.549: INFO:
Nov 23 15:55:23.550: INFO: The status of Pod calico-node-windows-cfkkl is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:23.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:23.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:23.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:23.550: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Nov 23 15:55:23.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:23.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:23.550: INFO: calico-node-windows-cfkkl capz-conf-5f845 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:54:28 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:55:22 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:55:22 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:57 +0000 UTC }]
Nov 23 15:55:23.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:23.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:23.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:23.550: INFO:
Nov 23 15:55:25.553: INFO: The status of Pod calico-node-windows-cfkkl is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:25.554: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:25.554: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:25.554: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:25.554: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Nov 23 15:55:25.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:25.554: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:25.554: INFO: calico-node-windows-cfkkl capz-conf-5f845 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:54:28 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:55:22 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:55:22 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:57 +0000 UTC }]
Nov 23 15:55:25.554: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:25.554: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:25.554: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:25.554: INFO:
Nov 23 15:55:27.733: INFO: The status of Pod calico-node-windows-cfkkl is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:27.734: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:27.734: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:27.734: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:27.734: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Nov 23 15:55:27.734: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:27.734: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:27.734: INFO: calico-node-windows-cfkkl capz-conf-5f845 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:54:28 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:55:22 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:55:22 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:57 +0000 UTC }]
Nov 23 15:55:27.734: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:27.734: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:27.734: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:27.734: INFO:
Nov 23 15:55:29.548: INFO: The status of Pod calico-node-windows-cfkkl is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:29.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:29.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:29.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:29.548: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Nov 23 15:55:29.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:29.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:29.548: INFO: calico-node-windows-cfkkl capz-conf-5f845 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:54:28 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:55:22 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:55:22 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:57 +0000 UTC }]
Nov 23 15:55:29.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:29.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:29.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:29.548: INFO:
Nov 23 15:55:31.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:31.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:31.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:31.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Nov 23 15:55:31.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:31.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:31.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:31.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:31.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:31.548: INFO:
Nov 23 15:55:33.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:33.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:33.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:33.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Nov 23 15:55:33.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:33.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:33.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:33.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:33.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:33.549: INFO:
Nov 23 15:55:35.554: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:35.554: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:35.554: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:35.554: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Nov 23 15:55:35.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:35.554: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:35.554: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:35.554: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:35.554: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:35.554: INFO:
Nov 23 15:55:37.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:37.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:37.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:37.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Nov 23 15:55:37.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:37.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:37.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:37.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:37.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:37.547: INFO:
Nov 23 15:55:39.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:39.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:39.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:39.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Nov 23 15:55:39.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:39.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:39.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:39.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:39.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:39.549: INFO:
Nov 23 15:55:41.732: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:41.732: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:41.732: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:41.732: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Nov 23 15:55:41.732: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:41.732: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:41.732: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:41.732: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:41.732: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:41.732: INFO:
Nov 23 15:55:43.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:43.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:43.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:43.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
Nov 23 15:55:43.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:43.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:43.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:43.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:43.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:43.548: INFO:
Nov 23 15:55:45.553: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:45.553: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:45.553: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:45.553: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
Nov 23 15:55:45.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:45.553: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:45.553: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:45.553: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:45.553: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:45.553: INFO:
Nov 23 15:55:47.553: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:47.553: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:47.553: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:47.553: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
Nov 23 15:55:47.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:47.553: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:47.553: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:47.553: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:47.553: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:47.553: INFO:
Nov 23 15:55:49.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:49.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:49.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:49.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
Nov 23 15:55:49.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:49.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:49.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:49.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:49.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:49.549: INFO:
Nov 23 15:55:51.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:51.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:51.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:51.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
Nov 23 15:55:51.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:51.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:51.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:51.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:51.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:51.549: INFO:
Nov 23 15:55:53.552: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:53.552: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:53.552: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:53.552: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
Nov 23 15:55:53.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:53.552: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:53.552: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:53.552: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:53.552: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:53.552: INFO:
Nov 23 15:55:55.552: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:55.552: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:55.552: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:55.552: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
Nov 23 15:55:55.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:55.552: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:55.552: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:55.552: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:55.552: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:55.552: INFO:
Nov 23 15:55:57.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:57.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:57.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:57.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
Nov 23 15:55:57.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:57.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:57.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:57.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:57.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:57.548: INFO:
Nov 23 15:55:59.560: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:59.560: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:59.560: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:55:59.560: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
Nov 23 15:55:59.560: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:55:59.560: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:55:59.560: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:59.560: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:59.560: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:55:59.560: INFO:
Nov 23 15:56:01.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:01.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:01.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:01.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
Nov 23 15:56:01.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:01.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:01.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:01.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:01.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:01.549: INFO:
Nov 23 15:56:03.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:03.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:03.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:03.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
Nov 23 15:56:03.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:03.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:03.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:03.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:03.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:03.549: INFO:
Nov 23 15:56:05.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:05.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:05.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:05.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
Nov 23 15:56:05.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:05.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:05.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:05.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:05.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:05.549: INFO:
Nov 23 15:56:07.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:07.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:07.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:07.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
Nov 23 15:56:07.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:07.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:07.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:07.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:07.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:07.548: INFO:
Nov 23 15:56:09.553: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:09.553: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:09.553: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:09.553: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
Nov 23 15:56:09.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:09.554: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:09.554: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:09.554: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:09.554: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:09.554: INFO:
Nov 23 15:56:11.553: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:11.553: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:11.553: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:11.553: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
Nov 23 15:56:11.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:11.553: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:11.553: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:11.553: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:11.553: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:11.553: INFO:
Nov 23 15:56:13.554: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:13.554: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:13.554: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:13.554: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
Nov 23 15:56:13.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:13.554: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:13.554: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:13.554: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:13.554: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:13.554: INFO:
Nov 23 15:56:15.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:15.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:15.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:15.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
Nov 23 15:56:15.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:15.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:15.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:15.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:15.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:15.550: INFO:
Nov 23 15:56:17.555: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:17.555: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:17.555: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:17.555: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
Nov 23 15:56:17.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:17.555: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:17.555: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:17.555: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:17.555: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:17.555: INFO:
Nov 23 15:56:19.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:19.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:19.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:19.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
Nov 23 15:56:19.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:19.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:19.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:19.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:19.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:19.549: INFO:
Nov 23 15:56:21.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:21.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:21.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:21.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
Nov 23 15:56:21.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:21.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:21.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:21.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:21.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:21.548: INFO:
Nov 23 15:56:23.554: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:23.554: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:23.554: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:23.554: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
Nov 23 15:56:23.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:23.554: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:23.554: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:23.554: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:23.554: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:23.554: INFO:
Nov 23 15:56:25.552: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:25.552: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:25.552: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:25.552: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
Nov 23 15:56:25.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:25.552: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:25.552: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:25.552: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:25.552: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:25.552: INFO:
Nov 23 15:56:27.554: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:27.554: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:27.554: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:27.554: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
Nov 23 15:56:27.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:27.554: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:27.554: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:27.554: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:27.554: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:27.554: INFO:
Nov 23 15:56:29.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:29.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:29.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:29.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
Nov 23 15:56:29.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:29.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:29.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:29.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:29.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:29.550: INFO:
Nov 23 15:56:31.551: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:31.551: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:31.551: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:31.551: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
Nov 23 15:56:31.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:31.551: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:31.551: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:31.551: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:31.551: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:31.551: INFO:
Nov 23 15:56:33.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:33.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:33.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:33.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
Nov 23 15:56:33.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:33.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:33.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:33.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:33.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:33.550: INFO:
Nov 23 15:56:35.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:35.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:35.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:35.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
Nov 23 15:56:35.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:35.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:35.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:35.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:35.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:35.550: INFO:
Nov 23 15:56:37.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:37.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:37.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:37.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
Nov 23 15:56:37.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:37.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:37.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:37.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:37.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:37.547: INFO:
Nov 23 15:56:39.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:39.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:39.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:39.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
Nov 23 15:56:39.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:39.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:39.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:39.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:39.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:39.547: INFO:
Nov 23 15:56:41.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:41.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:41.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:41.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
Nov 23 15:56:41.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:41.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:41.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:41.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:41.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:41.550: INFO:
Nov 23 15:56:43.554: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:43.554: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:43.554: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:43.554: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
Nov 23 15:56:43.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:43.554: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:43.554: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:43.554: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:43.554: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:43.554: INFO:
Nov 23 15:56:45.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:45.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:45.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:45.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
Nov 23 15:56:45.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:45.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:45.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:45.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:45.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:45.549: INFO:
Nov 23 15:56:47.552: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:47.552: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:47.553: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:47.553: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
Nov 23 15:56:47.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:47.553: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:47.553: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:47.553: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:47.553: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:47.553: INFO:
Nov 23 15:56:49.559: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:49.559: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:49.559: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:49.559: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
Nov 23 15:56:49.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:49.559: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:49.559: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:49.559: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:49.559: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:49.559: INFO:
Nov 23 15:56:51.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:51.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:51.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:51.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
Nov 23 15:56:51.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:51.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:51.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:51.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:51.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:51.550: INFO:
Nov 23 15:56:53.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:53.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:53.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:53.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
Nov 23 15:56:53.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:53.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:53.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:53.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:53.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:53.550: INFO:
Nov 23 15:56:55.557: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:55.557: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:55.557: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:55.557: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
Nov 23 15:56:55.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:55.557: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:55.557: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:55.557: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:55.557: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:55.557: INFO:
Nov 23 15:56:57.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:57.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:57.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:57.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
Nov 23 15:56:57.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:57.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:57.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:57.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:57.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:57.549: INFO:
Nov 23 15:56:59.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:59.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:59.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:56:59.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
Nov 23 15:56:59.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:56:59.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:56:59.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:59.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:59.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:56:59.549: INFO:
Nov 23 15:57:01.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:01.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:01.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:01.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
Nov 23 15:57:01.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:01.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:01.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:01.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:01.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:01.549: INFO:
Nov 23 15:57:03.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:03.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:03.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:03.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
Nov 23 15:57:03.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:03.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:03.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:03.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:03.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:03.547: INFO:
Nov 23 15:57:05.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:05.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:05.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:05.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
Nov 23 15:57:05.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:05.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:05.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:05.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:05.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:05.547: INFO:
Nov 23 15:57:07.555: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:07.555: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:07.555: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:07.555: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
Nov 23 15:57:07.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:07.555: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:07.555: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:07.555: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:07.555: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:07.555: INFO:
Nov 23 15:57:09.556: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:09.556: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:09.556: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:09.556: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
Nov 23 15:57:09.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:09.556: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:09.556: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:09.556: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:09.556: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:09.556: INFO:
Nov 23 15:57:11.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:11.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:11.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:11.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
Nov 23 15:57:11.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:11.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:11.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:11.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:11.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:11.548: INFO:
Nov 23 15:57:13.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:13.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:13.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:13.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
Nov 23 15:57:13.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:13.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:13.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:13.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:13.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:13.550: INFO:
Nov 23 15:57:15.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:15.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:15.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:15.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
Nov 23 15:57:15.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:15.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:15.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:15.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:15.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:15.549: INFO:
Nov 23 15:57:17.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:17.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:17.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:17.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
Nov 23 15:57:17.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:17.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:17.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:17.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:17.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:17.549: INFO:
Nov 23 15:57:19.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:19.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:19.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:19.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
Nov 23 15:57:19.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:19.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:19.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:19.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:19.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:19.546: INFO:
Nov 23 15:57:21.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:21.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:21.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:21.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
Nov 23 15:57:21.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:21.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:21.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:21.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:21.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:21.547: INFO:
Nov 23 15:57:23.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:23.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:23.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:23.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
Nov 23 15:57:23.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:23.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:23.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:23.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:23.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:23.547: INFO:
Nov 23 15:57:25.551: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:25.551: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:25.551: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:25.551: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
Nov 23 15:57:25.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:25.551: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:25.551: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:25.551: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:25.551: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:25.551: INFO:
Nov 23 15:57:27.553: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:27.553: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:27.553: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:27.553: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
Nov 23 15:57:27.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:27.553: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:27.553: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:27.553: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:27.553: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:27.553: INFO:
Nov 23 15:57:29.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:29.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:29.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:29.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
Nov 23 15:57:29.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:29.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:29.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:29.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:29.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:29.548: INFO:
Nov 23 15:57:31.552: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:31.552: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:31.552: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:31.552: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
Nov 23 15:57:31.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:31.552: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:31.552: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:31.552: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:31.552: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:31.552: INFO:
Nov 23 15:57:33.552: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:33.552: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:33.552: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:33.552: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
Nov 23 15:57:33.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:33.552: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:33.552: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:33.552: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:33.552: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:33.552: INFO:
Nov 23 15:57:35.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:35.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:35.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:35.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
Nov 23 15:57:35.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:35.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:35.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:35.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:35.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:35.549: INFO:
Nov 23 15:57:37.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:37.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:37.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:37.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
Nov 23 15:57:37.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:37.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:37.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:37.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:37.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:37.547: INFO:
Nov 23 15:57:39.554: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:39.554: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:39.554: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:39.554: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
Nov 23 15:57:39.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:39.554: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:39.554: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:39.554: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:39.554: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:39.554: INFO:
Nov 23 15:57:41.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:41.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:41.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:41.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
Nov 23 15:57:41.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:41.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:41.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:41.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:41.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:41.548: INFO:
Nov 23 15:57:43.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:43.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:43.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:43.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
Nov 23 15:57:43.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:43.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:43.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:43.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:43.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:43.547: INFO:
Nov 23 15:57:45.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:45.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:45.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:45.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
Nov 23 15:57:45.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:45.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:45.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:45.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:45.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:45.547: INFO:
Nov 23 15:57:47.557: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:47.557: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:47.557: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:47.557: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
Nov 23 15:57:47.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:47.557: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:47.557: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:47.557: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:47.557: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:47.557: INFO:
Nov 23 15:57:49.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:49.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:49.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:49.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
Nov 23 15:57:49.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:49.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:49.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:49.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:49.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:49.547: INFO:
Nov 23 15:57:51.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:51.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:51.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:51.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
Nov 23 15:57:51.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:51.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:51.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:51.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:51.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:51.548: INFO:
Nov 23 15:57:53.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:53.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:53.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:53.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
Nov 23 15:57:53.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:53.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:53.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:53.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:53.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:53.550: INFO:
Nov 23 15:57:55.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:55.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:55.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:55.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
Nov 23 15:57:55.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:55.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:55.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:55.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:55.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:55.547: INFO:
Nov 23 15:57:57.551: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:57.551: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:57.551: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:57.551: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
Nov 23 15:57:57.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:57.551: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:57.551: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:57.551: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:57.551: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:57.551: INFO:
Nov 23 15:57:59.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:59.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:59.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:57:59.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
Nov 23 15:57:59.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:57:59.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:57:59.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:59.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:59.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:57:59.550: INFO:
Nov 23 15:58:01.582: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:01.582: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:01.582: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:01.582: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
Nov 23 15:58:01.582: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:01.582: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:01.582: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:01.582: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:01.582: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:01.582: INFO:
Nov 23 15:58:03.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:03.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:03.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:03.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
Nov 23 15:58:03.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:03.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:03.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:03.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:03.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:03.548: INFO:
Nov 23 15:58:05.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:05.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:05.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:05.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
Nov 23 15:58:05.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:05.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:05.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:05.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:05.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:05.548: INFO:
Nov 23 15:58:07.551: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:07.551: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:07.551: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:07.551: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
Nov 23 15:58:07.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:07.551: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:07.551: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:07.551: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:07.551: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:07.551: INFO:
Nov 23 15:58:09.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:09.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:09.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:09.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
Nov 23 15:58:09.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:09.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:09.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:09.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:09.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:09.548: INFO:
Nov 23 15:58:11.552: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:11.552: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:11.552: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:11.552: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
Nov 23 15:58:11.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:11.552: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:11.552: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:11.552: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:11.552: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:11.552: INFO:
Nov 23 15:58:13.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:13.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:13.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:13.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
Nov 23 15:58:13.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:13.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:13.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:13.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:13.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:13.548: INFO:
Nov 23 15:58:15.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:15.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:15.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:15.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
Nov 23 15:58:15.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:15.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:15.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:15.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:15.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:15.549: INFO:
Nov 23 15:58:17.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:17.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:17.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:17.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
Nov 23 15:58:17.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:17.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:17.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:17.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:17.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:17.546: INFO:
Nov 23 15:58:19.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:19.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:19.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:19.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
Nov 23 15:58:19.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:19.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:19.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:19.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:19.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:19.546: INFO:
Nov 23 15:58:21.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:21.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:21.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:21.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
Nov 23 15:58:21.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:21.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:21.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:21.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:21.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:21.547: INFO:
Nov 23 15:58:23.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:23.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:23.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:23.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
Nov 23 15:58:23.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:23.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:23.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:23.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:23.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:23.546: INFO:
Nov 23 15:58:25.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:25.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:25.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:25.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
Nov 23 15:58:25.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:25.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:25.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:25.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:25.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:25.550: INFO:
Nov 23 15:58:27.555: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:27.555: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:27.555: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:27.555: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
Nov 23 15:58:27.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:27.555: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:27.555: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:27.555: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:27.555: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:27.555: INFO:
Nov 23 15:58:29.557: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:29.557: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:29.557: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:29.557: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
Nov 23 15:58:29.557: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:29.557: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:29.557: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:29.557: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:29.557: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:29.557: INFO:
Nov 23 15:58:31.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:31.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:31.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:31.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
Nov 23 15:58:31.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:31.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:31.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:31.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:31.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:31.548: INFO:
Nov 23 15:58:33.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:33.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:33.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:33.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
Nov 23 15:58:33.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:33.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:33.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:33.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:33.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:33.549: INFO:
Nov 23 15:58:35.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:35.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:35.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:35.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
Nov 23 15:58:35.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:35.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:35.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:35.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:35.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:35.549: INFO:
Nov 23 15:58:37.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:37.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:37.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:37.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
Nov 23 15:58:37.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:37.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:37.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:37.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:37.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:37.549: INFO:
Nov 23 15:58:39.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:39.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:39.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:39.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
Nov 23 15:58:39.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:39.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:39.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:39.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:39.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:39.547: INFO:
Nov 23 15:58:41.733: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:41.733: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:41.733: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:41.733: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
Nov 23 15:58:41.733: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:41.733: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:41.733: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:41.733: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:41.733: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:41.733: INFO:
Nov 23 15:58:43.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:43.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:43.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:43.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
Nov 23 15:58:43.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:43.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:43.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:43.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:43.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:43.549: INFO:
Nov 23 15:58:45.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:45.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:45.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:45.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
Nov 23 15:58:45.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:45.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:45.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:45.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:45.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:45.549: INFO:
Nov 23 15:58:47.559: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:47.559: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:47.559: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:47.559: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
Nov 23 15:58:47.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:47.559: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:47.559: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:47.559: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:47.559: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:47.559: INFO:
Nov 23 15:58:49.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:49.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:49.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:49.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
Nov 23 15:58:49.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:49.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:49.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:49.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:49.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:49.550: INFO:
Nov 23 15:58:51.556: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:51.556: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:51.556: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:51.556: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
Nov 23 15:58:51.556: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:51.556: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:51.556: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:51.556: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:51.556: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:51.556: INFO:
Nov 23 15:58:53.560: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:53.560: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:53.560: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:53.560: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
Nov 23 15:58:53.560: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:53.560: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:53.560: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:53.560: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:53.560: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:53.560: INFO:
Nov 23 15:58:55.553: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:55.553: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:55.553: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:55.553: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
Nov 23 15:58:55.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:55.553: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:55.553: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:55.553: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:55.553: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:55.553: INFO:
Nov 23 15:58:57.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:57.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:57.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:57.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
Nov 23 15:58:57.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:57.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:57.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:57.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:57.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:57.547: INFO:
Nov 23 15:58:59.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:59.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:59.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:58:59.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
Nov 23 15:58:59.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:58:59.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:58:59.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:59.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:59.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:58:59.546: INFO:
Nov 23 15:59:01.552: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:01.552: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:01.552: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:01.552: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
Nov 23 15:59:01.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:01.552: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:01.552: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:01.552: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:01.552: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:01.552: INFO:
Nov 23 15:59:03.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:03.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:03.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:03.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
Nov 23 15:59:03.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:03.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:03.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:03.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:03.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:03.548: INFO:
Nov 23 15:59:05.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:05.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:05.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:05.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
Nov 23 15:59:05.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:05.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:05.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:05.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:05.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:05.548: INFO:
Nov 23 15:59:07.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:07.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:07.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:07.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
Nov 23 15:59:07.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:07.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:07.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:07.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:07.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:07.545: INFO:
Nov 23 15:59:09.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:09.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:09.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:09.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
Nov 23 15:59:09.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:09.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:09.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:09.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:09.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:09.548: INFO:
Nov 23 15:59:11.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:11.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:11.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:11.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
Nov 23 15:59:11.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:11.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:11.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:11.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:11.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:11.544: INFO:
Nov 23 15:59:13.558: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:13.558: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:13.558: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:13.558: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
Nov 23 15:59:13.558: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:13.558: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:13.558: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:13.558: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:13.558: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:13.558: INFO:
Nov 23 15:59:15.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:15.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:15.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:15.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
Nov 23 15:59:15.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:15.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:15.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:15.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:15.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:15.544: INFO:
Nov 23 15:59:17.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:17.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:17.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:17.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
Nov 23 15:59:17.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:17.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:17.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:17.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:17.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:17.545: INFO:
Nov 23 15:59:19.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:19.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:19.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:19.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
Nov 23 15:59:19.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:19.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:19.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:19.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:19.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:19.544: INFO:
Nov 23 15:59:21.552: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:21.552: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:21.552: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:21.552: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
Nov 23 15:59:21.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:21.552: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:21.552: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:21.552: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:21.552: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:21.552: INFO:
Nov 23 15:59:23.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:23.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:23.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:23.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
Nov 23 15:59:23.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:23.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:23.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:23.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:23.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:23.544: INFO:
Nov 23 15:59:25.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:25.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:25.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:25.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
Nov 23 15:59:25.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:25.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:25.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:25.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:25.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:25.546: INFO:
Nov 23 15:59:27.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:27.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:27.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:27.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
Nov 23 15:59:27.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:27.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:27.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:27.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:27.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:27.544: INFO:
Nov 23 15:59:29.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:29.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:29.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:29.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
Nov 23 15:59:29.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:29.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:29.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:29.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:29.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:29.545: INFO:
Nov 23 15:59:31.553: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:31.553: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:31.553: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:31.553: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
Nov 23 15:59:31.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:31.553: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:31.553: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:31.553: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:31.553: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:31.553: INFO:
Nov 23 15:59:33.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:33.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:33.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:33.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
Nov 23 15:59:33.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:33.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:33.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:33.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:33.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:33.544: INFO:
Nov 23 15:59:35.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:35.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:35.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:35.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
Nov 23 15:59:35.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:35.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:35.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:35.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:35.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:35.544: INFO:
Nov 23 15:59:37.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:37.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:37.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:37.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
Nov 23 15:59:37.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:37.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:37.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:37.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:37.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:37.545: INFO:
Nov 23 15:59:39.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:39.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:39.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:39.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
Nov 23 15:59:39.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:39.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:39.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:39.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:39.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:39.545: INFO:
Nov 23 15:59:41.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:41.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:41.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:41.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
Nov 23 15:59:41.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:41.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:41.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:41.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:41.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:41.549: INFO:
Nov 23 15:59:43.733: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:43.733: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:43.733: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:43.733: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
Nov 23 15:59:43.733: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:43.733: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:43.733: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:43.733: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:43.733: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:43.733: INFO:
Nov 23 15:59:45.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:45.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:45.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:45.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
Nov 23 15:59:45.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:45.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:45.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:45.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:45.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:45.543: INFO:
Nov 23 15:59:47.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:47.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:47.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:47.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
Nov 23 15:59:47.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:47.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:47.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:47.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:47.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:47.543: INFO:
Nov 23 15:59:49.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:49.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:49.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:49.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
Nov 23 15:59:49.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:49.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:49.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:49.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:49.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:49.545: INFO:
Nov 23 15:59:51.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:51.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:51.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:51.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
Nov 23 15:59:51.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:51.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:51.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:51.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:51.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:51.545: INFO:
Nov 23 15:59:53.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:53.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:53.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:53.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
Nov 23 15:59:53.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:53.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:53.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:53.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:53.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:53.545: INFO:
Nov 23 15:59:55.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:55.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:55.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:55.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
Nov 23 15:59:55.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:55.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:55.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:55.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:55.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:55.547: INFO:
Nov 23 15:59:57.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:57.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:57.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:57.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
Nov 23 15:59:57.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:57.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:57.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:57.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:57.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:57.545: INFO:
Nov 23 15:59:59.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:59.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:59.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 15:59:59.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
Nov 23 15:59:59.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 15:59:59.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 15:59:59.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:59.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:59.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 15:59:59.543: INFO:
Nov 23 16:00:01.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:01.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:01.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:01.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
Nov 23 16:00:01.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:01.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:01.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:01.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:01.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:01.544: INFO:
Nov 23 16:00:03.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:03.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:03.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:03.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
Nov 23 16:00:03.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:03.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:03.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:03.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:03.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:03.545: INFO:
Nov 23 16:00:05.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:05.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:05.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:05.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
Nov 23 16:00:05.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:05.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:05.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:05.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:05.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:05.547: INFO:
Nov 23 16:00:07.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:07.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:07.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:07.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
Nov 23 16:00:07.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:07.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:07.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:07.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:07.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:07.550: INFO:
Nov 23 16:00:09.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:09.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:09.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:09.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
Nov 23 16:00:09.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:09.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:09.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:09.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:09.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:09.547: INFO:
Nov 23 16:00:11.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:11.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:11.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:11.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
Nov 23 16:00:11.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:11.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:11.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:11.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:11.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:11.546: INFO:
Nov 23 16:00:13.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:13.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:13.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:13.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
Nov 23 16:00:13.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:13.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:13.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:13.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:13.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:13.549: INFO:
Nov 23 16:00:15.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:15.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:15.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:15.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
Nov 23 16:00:15.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:15.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:15.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:15.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:15.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:15.548: INFO:
Nov 23 16:00:17.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:17.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:17.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:17.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
Nov 23 16:00:17.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:17.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:17.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:17.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:17.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:17.546: INFO:
Nov 23 16:00:19.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:19.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:19.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:19.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
Nov 23 16:00:19.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:19.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:19.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:19.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:19.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:19.546: INFO:
Nov 23 16:00:21.727: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:21.727: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:21.727: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:21.727: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
Nov 23 16:00:21.727: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:21.727: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:21.727: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:21.727: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:21.727: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:21.727: INFO:
Nov 23 16:00:23.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:23.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:23.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:23.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
Nov 23 16:00:23.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:23.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:23.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:23.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:23.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:23.547: INFO:
Nov 23 16:00:25.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:25.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:25.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:25.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
Nov 23 16:00:25.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:25.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:25.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:25.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:25.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:25.546: INFO:
Nov 23 16:00:27.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:27.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:27.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:27.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
Nov 23 16:00:27.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:27.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:27.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:27.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:27.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:27.550: INFO:
Nov 23 16:00:29.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:29.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:29.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:29.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
Nov 23 16:00:29.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:29.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:29.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:29.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:29.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:29.543: INFO:
Nov 23 16:00:31.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:31.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:31.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:31.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
Nov 23 16:00:31.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:31.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:31.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:31.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:31.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:31.548: INFO:
Nov 23 16:00:33.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:33.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:33.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:33.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
Nov 23 16:00:33.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:33.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:33.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:33.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:33.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:33.544: INFO:
Nov 23 16:00:35.553: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:35.553: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:35.553: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:35.553: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
Nov 23 16:00:35.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:35.553: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:35.553: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:35.553: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:35.553: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:35.553: INFO:
Nov 23 16:00:37.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:37.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:37.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:37.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
Nov 23 16:00:37.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:37.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:37.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:37.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:37.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:37.544: INFO:
Nov 23 16:00:39.555: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:39.555: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:39.555: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:39.555: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
Nov 23 16:00:39.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:39.555: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:39.555: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:39.555: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:39.555: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:39.555: INFO:
Nov 23 16:00:41.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:41.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:41.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:41.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
Nov 23 16:00:41.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:41.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:41.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:41.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:41.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:41.549: INFO:
Nov 23 16:00:43.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:43.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:43.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:43.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
Nov 23 16:00:43.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:43.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:43.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:43.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:43.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:43.546: INFO:
Nov 23 16:00:45.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:45.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:45.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:45.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
Nov 23 16:00:45.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:45.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:45.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:45.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:45.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:45.547: INFO:
Nov 23 16:00:47.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:47.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:47.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:47.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
Nov 23 16:00:47.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:47.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:47.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:47.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:47.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:47.548: INFO:
Nov 23 16:00:49.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:49.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:49.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:49.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
Nov 23 16:00:49.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:49.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:49.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:49.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:49.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:49.545: INFO:
Nov 23 16:00:51.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:51.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:51.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:51.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
Nov 23 16:00:51.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:51.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:51.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:51.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:51.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:51.545: INFO:
Nov 23 16:00:53.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:53.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:53.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:53.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
Nov 23 16:00:53.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:53.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:53.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:53.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:53.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:53.548: INFO:
Nov 23 16:00:55.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:55.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:55.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:55.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
Nov 23 16:00:55.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:55.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:55.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:55.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:55.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:55.545: INFO:
Nov 23 16:00:57.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:57.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:57.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:57.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
Nov 23 16:00:57.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:57.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:57.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:57.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:57.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:57.547: INFO:
Nov 23 16:00:59.552: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:59.552: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:59.552: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:00:59.552: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
Nov 23 16:00:59.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:00:59.552: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:00:59.552: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:59.552: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:59.552: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:00:59.552: INFO:
Nov 23 16:01:01.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:01.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:01.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:01.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
Nov 23 16:01:01.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:01.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:01.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:01.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:01.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:01.549: INFO:
Nov 23 16:01:03.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:03.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:03.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:03.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
Nov 23 16:01:03.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:03.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:03.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:03.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:03.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:03.549: INFO:
Nov 23 16:01:05.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:05.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:05.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:05.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
Nov 23 16:01:05.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:05.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:05.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:05.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:05.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:05.545: INFO:
Nov 23 16:01:07.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:07.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:07.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:07.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
Nov 23 16:01:07.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:07.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:07.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:07.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:07.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:07.550: INFO:
Nov 23 16:01:09.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:09.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:09.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:09.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
Nov 23 16:01:09.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:09.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:09.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:09.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:09.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:09.545: INFO:
Nov 23 16:01:11.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:11.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:11.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:11.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
Nov 23 16:01:11.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:11.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:11.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:11.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:11.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:11.545: INFO:
Nov 23 16:01:13.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:13.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:13.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:13.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
Nov 23 16:01:13.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:13.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:13.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:13.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:13.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:13.547: INFO:
Nov 23 16:01:15.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:15.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:15.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:15.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
Nov 23 16:01:15.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:15.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:15.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:15.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:15.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:15.545: INFO:
Nov 23 16:01:17.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:17.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:17.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:17.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
Nov 23 16:01:17.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:17.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:17.551: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:17.551: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:17.551: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:17.551: INFO:
Nov 23 16:01:19.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:19.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:19.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:19.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
Nov 23 16:01:19.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:19.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:19.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:19.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:19.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:19.546: INFO:
Nov 23 16:01:21.551: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:21.551: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:21.551: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:21.551: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
Nov 23 16:01:21.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:21.551: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:21.551: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:21.551: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:21.551: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:21.551: INFO:
Nov 23 16:01:23.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:23.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:23.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:23.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
Nov 23 16:01:23.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:23.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:23.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:23.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:23.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:23.547: INFO:
Nov 23 16:01:25.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:25.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:25.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:25.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
Nov 23 16:01:25.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:25.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:25.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:25.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:25.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:25.546: INFO:
Nov 23 16:01:27.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:27.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:27.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:27.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
Nov 23 16:01:27.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:27.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:27.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:27.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:27.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:27.543: INFO:
Nov 23 16:01:29.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:29.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:29.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:29.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
Nov 23 16:01:29.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:29.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:29.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:29.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:29.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:29.543: INFO:
Nov 23 16:01:31.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:31.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:31.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:31.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
Nov 23 16:01:31.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:31.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:31.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:31.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:31.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:31.547: INFO:
Nov 23 16:01:33.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:33.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:33.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:33.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
Nov 23 16:01:33.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:33.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:33.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:33.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:33.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:33.549: INFO:
Nov 23 16:01:35.552: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:35.552: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:35.552: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:35.552: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
Nov 23 16:01:35.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:35.552: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:35.552: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:35.552: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:35.552: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:35.552: INFO:
Nov 23 16:01:37.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:37.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:37.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:37.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
Nov 23 16:01:37.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:37.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:37.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:37.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:37.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:37.544: INFO:
Nov 23 16:01:39.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:39.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:39.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:39.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
Nov 23 16:01:39.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:39.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:39.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:39.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:39.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:39.548: INFO:
Nov 23 16:01:41.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:41.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:41.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:41.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
Nov 23 16:01:41.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:41.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:41.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:41.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:41.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:41.550: INFO:
Nov 23 16:01:43.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:43.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:43.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:43.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
Nov 23 16:01:43.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:43.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:43.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:43.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:43.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:43.546: INFO:
Nov 23 16:01:45.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:45.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:45.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:45.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
Nov 23 16:01:45.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:45.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:45.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:45.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:45.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:45.546: INFO:
Nov 23 16:01:47.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:47.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:47.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:47.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
Nov 23 16:01:47.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:47.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:47.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:47.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:47.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:47.544: INFO:
Nov 23 16:01:49.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:49.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:49.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:49.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
Nov 23 16:01:49.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:49.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:49.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:49.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:49.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:49.543: INFO:
Nov 23 16:01:51.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:51.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:51.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:51.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
Nov 23 16:01:51.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:51.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:51.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:51.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:51.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:51.547: INFO:
Nov 23 16:01:53.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:53.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:53.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:53.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
Nov 23 16:01:53.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:53.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:53.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:53.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:53.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:53.544: INFO:
Nov 23 16:01:55.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:55.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:55.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:55.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
Nov 23 16:01:55.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:55.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:55.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:55.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:55.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:55.548: INFO:
Nov 23 16:01:57.555: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:57.555: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:57.555: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:57.555: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
Nov 23 16:01:57.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:57.555: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:57.555: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:57.555: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:57.555: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:57.555: INFO:
Nov 23 16:01:59.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:59.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:59.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:01:59.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
Nov 23 16:01:59.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:01:59.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:01:59.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:59.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:59.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:01:59.543: INFO:
Nov 23 16:02:01.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:01.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:01.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:01.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
Nov 23 16:02:01.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:01.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:01.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:01.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:01.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:01.547: INFO:
Nov 23 16:02:03.551: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:03.551: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:03.551: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:03.551: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
Nov 23 16:02:03.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:03.551: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:03.551: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:03.551: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:03.552: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:03.552: INFO:
Nov 23 16:02:05.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:05.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:05.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:05.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
Nov 23 16:02:05.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:05.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:05.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:05.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:05.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:05.545: INFO:
Nov 23 16:02:07.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:07.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:07.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:07.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
Nov 23 16:02:07.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:07.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:07.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:07.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:07.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:07.548: INFO:
Nov 23 16:02:09.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:09.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:09.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:09.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
Nov 23 16:02:09.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:09.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:09.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:09.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:09.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:09.545: INFO:
Nov 23 16:02:11.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:11.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:11.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:11.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
Nov 23 16:02:11.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:11.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:11.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:11.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:11.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:11.548: INFO:
Nov 23 16:02:13.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:13.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:13.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:13.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
Nov 23 16:02:13.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:13.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:13.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:13.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:13.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:13.547: INFO:
Nov 23 16:02:15.553: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:15.553: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:15.553: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:15.553: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
Nov 23 16:02:15.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:15.553: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:15.553: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:15.553: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:15.553: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:15.553: INFO:
Nov 23 16:02:17.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:17.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:17.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:17.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
Nov 23 16:02:17.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:17.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:17.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:17.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:17.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:17.543: INFO:
Nov 23 16:02:19.552: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:19.552: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:19.552: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:19.552: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
Nov 23 16:02:19.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:19.552: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:19.552: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:19.552: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:19.552: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:19.552: INFO:
Nov 23 16:02:21.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:21.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:21.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:21.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
Nov 23 16:02:21.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:21.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:21.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:21.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:21.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:21.543: INFO:
Nov 23 16:02:23.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:23.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:23.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:23.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
Nov 23 16:02:23.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:23.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:23.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:23.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:23.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:23.546: INFO:
Nov 23 16:02:25.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:25.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:25.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:25.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
Nov 23 16:02:25.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:25.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:25.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:25.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:25.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:25.545: INFO:
Nov 23 16:02:27.560: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:27.560: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:27.560: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:27.560: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
Nov 23 16:02:27.560: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:27.560: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:27.561: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:27.561: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:27.561: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:27.561: INFO:
Nov 23 16:02:29.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:29.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:29.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:29.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
Nov 23 16:02:29.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:29.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:29.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:29.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:29.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:29.546: INFO:
Nov 23 16:02:31.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:31.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:31.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:31.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
Nov 23 16:02:31.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:31.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:31.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:31.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:31.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:31.544: INFO:
Nov 23 16:02:33.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:33.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:33.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:33.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
Nov 23 16:02:33.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:33.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:33.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:33.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:33.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:33.544: INFO:
Nov 23 16:02:35.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:35.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:35.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:35.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
Nov 23 16:02:35.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:35.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:35.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:35.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:35.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:35.549: INFO:
Nov 23 16:02:37.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:37.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:37.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:37.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
Nov 23 16:02:37.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:37.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:37.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:37.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:37.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:37.544: INFO:
Nov 23 16:02:39.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:39.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:39.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:39.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
Nov 23 16:02:39.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:39.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:39.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:39.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:39.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:39.550: INFO:
Nov 23 16:02:41.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:41.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:41.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:41.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
Nov 23 16:02:41.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:41.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:41.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:41.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:41.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:41.548: INFO:
Nov 23 16:02:43.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:43.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:43.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:43.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
Nov 23 16:02:43.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:43.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:43.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:43.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:43.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:43.543: INFO:
Nov 23 16:02:45.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:45.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:45.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:45.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
Nov 23 16:02:45.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:45.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:45.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:45.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:45.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:45.545: INFO:
Nov 23 16:02:47.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:47.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:47.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:47.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
Nov 23 16:02:47.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:47.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:47.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:47.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:47.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:47.546: INFO:
Nov 23 16:02:49.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:49.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:49.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:49.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
Nov 23 16:02:49.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:49.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:49.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:49.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:49.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:49.543: INFO:
Nov 23 16:02:51.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:51.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:51.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:51.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
Nov 23 16:02:51.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:51.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:51.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:51.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:51.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:51.545: INFO:
Nov 23 16:02:53.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:53.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:53.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:53.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
Nov 23 16:02:53.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:53.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:53.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:53.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:53.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:53.545: INFO:
Nov 23 16:02:55.552: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:55.552: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:55.552: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:55.552: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
Nov 23 16:02:55.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:55.552: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:55.552: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:55.552: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:55.552: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:55.552: INFO:
Nov 23 16:02:57.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:57.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:57.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:57.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
Nov 23 16:02:57.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:57.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:57.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:57.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:57.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:57.548: INFO:
Nov 23 16:02:59.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:59.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:59.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:02:59.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
Nov 23 16:02:59.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:02:59.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:02:59.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:59.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:59.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:02:59.546: INFO:
Nov 23 16:03:01.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:01.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:01.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:01.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
Nov 23 16:03:01.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:01.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:01.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:01.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:01.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:01.549: INFO:
Nov 23 16:03:03.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:03.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:03.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:03.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
Nov 23 16:03:03.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:03.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:03.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:03.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:03.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:03.544: INFO:
Nov 23 16:03:05.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:05.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:05.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:05.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
Nov 23 16:03:05.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:05.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:05.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:05.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:05.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:05.546: INFO:
Nov 23 16:03:07.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:07.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:07.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:07.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
Nov 23 16:03:07.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:07.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:07.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:07.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:07.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:07.544: INFO:
Nov 23 16:03:09.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:09.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:09.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:09.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
Nov 23 16:03:09.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:09.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:09.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:09.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:09.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:09.543: INFO:
Nov 23 16:03:11.555: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:11.555: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:11.555: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:11.555: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
Nov 23 16:03:11.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:11.555: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:11.555: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:11.555: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:11.555: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:11.555: INFO:
Nov 23 16:03:13.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:13.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:13.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:13.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
Nov 23 16:03:13.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:13.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:13.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:13.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:13.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:13.548: INFO:
Nov 23 16:03:15.551: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:15.551: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:15.551: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:15.551: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
Nov 23 16:03:15.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:15.551: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:15.551: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:15.551: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:15.551: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:15.551: INFO:
Nov 23 16:03:17.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:17.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:17.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:17.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
Nov 23 16:03:17.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:17.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:17.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:17.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:17.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:17.545: INFO:
Nov 23 16:03:19.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:19.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:19.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:19.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
Nov 23 16:03:19.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:19.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:19.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:19.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:19.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:19.546: INFO:
Nov 23 16:03:21.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:21.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:21.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:21.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
Nov 23 16:03:21.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:21.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:21.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:21.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:21.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:21.550: INFO:
Nov 23 16:03:23.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:23.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:23.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:23.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
Nov 23 16:03:23.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:23.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:23.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:23.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:23.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:23.547: INFO:
Nov 23 16:03:25.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:25.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:25.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:25.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
Nov 23 16:03:25.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:25.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:25.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:25.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:25.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:25.543: INFO:
Nov 23 16:03:27.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:27.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:27.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:27.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
Nov 23 16:03:27.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:27.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:27.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:27.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:27.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:27.544: INFO:
Nov 23 16:03:29.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:29.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:29.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:29.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
Nov 23 16:03:29.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:29.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:29.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:29.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:29.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:29.544: INFO:
Nov 23 16:03:31.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:31.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:31.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:31.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
Nov 23 16:03:31.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:31.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:31.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:31.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:31.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:31.546: INFO:
Nov 23 16:03:33.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:33.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:33.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:33.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
Nov 23 16:03:33.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:33.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:33.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:33.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:33.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:33.546: INFO:
Nov 23 16:03:35.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:35.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:35.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:35.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
Nov 23 16:03:35.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:35.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:35.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:35.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:35.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:35.550: INFO:
Nov 23 16:03:37.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:37.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:37.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:37.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
Nov 23 16:03:37.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:37.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:37.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:37.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:37.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:37.545: INFO:
Nov 23 16:03:39.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:39.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:39.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:39.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
Nov 23 16:03:39.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:39.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:39.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:39.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:39.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:39.545: INFO:
Nov 23 16:03:41.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:41.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:41.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:41.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
Nov 23 16:03:41.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:41.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:41.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:41.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:41.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:41.550: INFO:
Nov 23 16:03:43.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:43.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:43.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:43.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
Nov 23 16:03:43.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:43.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:43.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:43.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:43.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:43.546: INFO:
Nov 23 16:03:45.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:45.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:45.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:45.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
Nov 23 16:03:45.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:45.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:45.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:45.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:45.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:45.545: INFO:
Nov 23 16:03:47.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:47.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:47.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:47.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
Nov 23 16:03:47.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:47.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:47.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:47.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:47.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:47.543: INFO:
Nov 23 16:03:49.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:49.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:49.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:49.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
Nov 23 16:03:49.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:49.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:49.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:49.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:49.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:49.546: INFO:
Nov 23 16:03:51.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:51.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:51.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:51.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
Nov 23 16:03:51.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:51.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:51.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:51.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:51.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:51.546: INFO:
Nov 23 16:03:53.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:53.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:53.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:53.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
Nov 23 16:03:53.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:53.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:53.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:53.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:53.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:53.548: INFO:
Nov 23 16:03:55.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:55.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:55.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:55.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
Nov 23 16:03:55.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:55.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:55.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:55.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:55.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:55.548: INFO:
Nov 23 16:03:57.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:57.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:57.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:57.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
Nov 23 16:03:57.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:57.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:57.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:57.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:57.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:57.547: INFO:
Nov 23 16:03:59.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:59.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:59.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:03:59.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
Nov 23 16:03:59.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:03:59.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:03:59.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:59.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:59.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:03:59.549: INFO:
Nov 23 16:04:01.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:01.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:01.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:01.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
Nov 23 16:04:01.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:01.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:01.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:01.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:01.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:01.543: INFO:
Nov 23 16:04:03.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:03.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:03.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:03.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
Nov 23 16:04:03.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:03.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:03.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:03.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:03.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:03.546: INFO:
Nov 23 16:04:05.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:05.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:05.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:05.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
Nov 23 16:04:05.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:05.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:05.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:05.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:05.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:05.545: INFO:
Nov 23 16:04:07.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:07.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:07.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:07.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
Nov 23 16:04:07.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:07.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:07.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:07.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:07.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:07.544: INFO:
Nov 23 16:04:09.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:09.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:09.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:09.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
Nov 23 16:04:09.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:09.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:09.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:09.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:09.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:09.544: INFO:
Nov 23 16:04:11.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:11.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:11.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:11.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
Nov 23 16:04:11.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:11.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:11.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:11.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:11.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:11.544: INFO:
Nov 23 16:04:13.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:13.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:13.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:13.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
Nov 23 16:04:13.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:13.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:13.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:13.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:13.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:13.543: INFO:
Nov 23 16:04:15.726: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:15.726: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:15.726: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:15.726: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
Nov 23 16:04:15.726: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:15.726: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:15.726: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:15.726: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:15.726: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:15.726: INFO:
Nov 23 16:04:17.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:17.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:17.548: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:17.548: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
Nov 23 16:04:17.548: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:17.548: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:17.548: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:17.548: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:17.548: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:17.548: INFO:
Nov 23 16:04:19.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:19.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:19.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:19.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
Nov 23 16:04:19.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:19.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:19.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:19.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:19.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:19.544: INFO:
Nov 23 16:04:21.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:21.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:21.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:21.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
Nov 23 16:04:21.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:21.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:21.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:21.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:21.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:21.546: INFO:
Nov 23 16:04:23.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:23.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:23.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:23.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
Nov 23 16:04:23.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:23.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:23.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:23.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:23.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:23.543: INFO:
Nov 23 16:04:25.547: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:25.547: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:25.547: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:25.547: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
Nov 23 16:04:25.547: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:25.547: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:25.547: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:25.547: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:25.547: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:25.547: INFO:
Nov 23 16:04:27.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:27.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:27.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:27.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
Nov 23 16:04:27.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:27.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:27.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:27.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:27.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:27.545: INFO:
Nov 23 16:04:29.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:29.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:29.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:29.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
Nov 23 16:04:29.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:29.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:29.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:29.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:29.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:29.546: INFO:
Nov 23 16:04:31.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:31.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:31.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:31.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
Nov 23 16:04:31.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:31.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:31.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:31.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:31.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:31.546: INFO:
Nov 23 16:04:33.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:33.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:33.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:33.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
Nov 23 16:04:33.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:33.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:33.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:33.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:33.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:33.546: INFO:
Nov 23 16:04:35.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:35.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:35.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:35.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
Nov 23 16:04:35.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:35.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:35.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:35.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:35.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:35.546: INFO:
Nov 23 16:04:37.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:37.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:37.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:37.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
Nov 23 16:04:37.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:37.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:37.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:37.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:37.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:37.543: INFO:
Nov 23 16:04:39.551: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:39.551: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:39.551: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:39.551: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
Nov 23 16:04:39.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:39.551: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:39.551: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:39.551: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:39.551: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:39.551: INFO:
Nov 23 16:04:41.549: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:41.549: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:41.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:41.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
Nov 23 16:04:41.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:41.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:41.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:41.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:41.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:41.549: INFO:
Nov 23 16:04:43.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:43.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:43.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:43.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
Nov 23 16:04:43.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:43.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:43.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:43.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:43.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:43.546: INFO:
Nov 23 16:04:45.545: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:45.545: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:45.545: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:45.545: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
Nov 23 16:04:45.545: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:45.545: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:45.545: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:45.545: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:45.545: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:45.545: INFO:
Nov 23 16:04:47.550: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:47.550: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:47.550: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:47.550: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
Nov 23 16:04:47.550: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:47.550: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:47.550: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:47.550: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:47.550: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:47.550: INFO:
Nov 23 16:04:49.543: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:49.543: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:49.543: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:49.543: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
Nov 23 16:04:49.543: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:49.543: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:49.543: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:49.543: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:49.543: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:49.543: INFO:
Nov 23 16:04:51.544: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:51.544: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:51.544: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:51.544: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
Nov 23 16:04:51.544: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:51.544: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:51.544: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:51.544: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:51.544: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:51.544: INFO:
Nov 23 16:04:53.555: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:53.555: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:53.555: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:53.555: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
Nov 23 16:04:53.555: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:53.555: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:53.555: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:53.555: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:53.555: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:53.555: INFO:
Nov 23 16:04:55.546: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:55.546: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:55.546: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:55.546: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
Nov 23 16:04:55.546: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:55.546: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:55.546: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:55.546: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:55.546: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:55.546: INFO:
Nov 23 16:04:57.733: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:57.733: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:57.733: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:57.733: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
Nov 23 16:04:57.733: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:57.733: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:57.733: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:57.733: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:57.733: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:57.733: INFO:
Nov 23 16:04:59.552: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:59.552: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:59.552: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:04:59.552: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
Nov 23 16:04:59.552: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:04:59.552: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:04:59.552: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:59.552: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:59.552: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:04:59.552: INFO:
Nov 23 16:05:01.551: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:01.551: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:01.551: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:01.551: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
Nov 23 16:05:01.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:05:01.551: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:05:01.551: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:01.551: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:01.551: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:01.551: INFO:
Nov 23 16:05:03.548: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:03.548: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:03.549: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:03.549: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
Nov 23 16:05:03.549: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:05:03.549: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:05:03.549: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:03.549: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:03.549: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:03.549: INFO:
Nov 23 16:05:05.551: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:05.551: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:05.551: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:05.551: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
Nov 23 16:05:05.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:05:05.551: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:05:05.551: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:05.551: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:05.551: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:05.551: INFO:
Nov 23 16:05:07.553: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:07.553: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:07.553: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:07.553: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
Nov 23 16:05:07.553: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:05:07.553: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:05:07.553: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:07.553: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:07.553: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:07.553: INFO:
Nov 23 16:05:09.551: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:09.551: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:09.551: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:09.551: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Nov 23 16:05:09.551: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:05:09.551: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:05:09.551: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:09.551: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:09.551: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:09.551: INFO:
Nov 23 16:05:11.554: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:11.554: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:11.554: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:11.554: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Nov 23 16:05:11.554: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:05:11.554: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:05:11.554: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:11.554: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:11.554: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:11.554: INFO:
Nov 23 16:05:13.559: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:13.559: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:13.559: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:13.559: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 23 16:05:13.559: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:05:13.559: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:05:13.559: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:13.559: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:13.559: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:13.559: INFO:
Nov 23 16:05:13.949: INFO: The status of Pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:13.949: INFO: The status of Pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:13.949: INFO: The status of Pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 23 16:05:13.949: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (601 seconds elapsed)
Nov 23 16:05:13.949: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 23 16:05:13.949: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:05:13.949: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:13.949: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:13.949: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:13.949: INFO:
�[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m11/23/22 16:05:13.949�[0m
�[1mSTEP:�[0m Found 126 events. �[38;5;243m11/23/22 16:05:14.095�[0m
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:49:36 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-e0y1lq-control-plane-2k75s_7414a6ef-ca20-45f3-8ab5-daf3def37d30 became leader
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:49:39 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-e0y1lq-control-plane-2k75s_57c9ca48-1e24-4db4-b309-f26ecbdc1bcb became leader
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:49:43 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-787d4945fb to 2
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:49:43 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-789pf
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:49:43 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-ntnmt
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:49:43 +0000 UTC - event for coredns-787d4945fb-789pf: {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 23 16:05:14.096: INFO: At 2022-11-23 15:49:43 +0000 UTC - event for coredns-787d4945fb-ntnmt: {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 23 16:05:14.096: INFO: At 2022-11-23 15:49:43 +0000 UTC - event for etcd-capz-conf-e0y1lq-control-plane-2k75s: {node-controller } NodeNotReady: Node is not ready
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:49:43 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-hcv54
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:49:43 +0000 UTC - event for kube-proxy-hcv54: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-hcv54 to capz-conf-e0y1lq-control-plane-2k75s
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:49:44 +0000 UTC - event for kube-proxy-hcv54: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.40_4d1daf69064132"
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:49:50 +0000 UTC - event for kube-proxy-hcv54: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.40_4d1daf69064132" in 5.994837089s (5.99484419s including waiting)
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:49:50 +0000 UTC - event for kube-proxy-hcv54: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Created: Created container kube-proxy
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:49:50 +0000 UTC - event for kube-proxy-hcv54: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Started: Started container kube-proxy
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:50:06 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:50:06 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-c5wk2
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:50:06 +0000 UTC - event for metrics-server-c9574f845-c5wk2: {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 23 16:05:14.096: INFO: At 2022-11-23 15:50:08 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:50:08 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-djfgq
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:50:08 +0000 UTC - event for calico-kube-controllers-657b584867-djfgq: {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 23 16:05:14.096: INFO: At 2022-11-23 15:50:09 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-xnkg8
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:50:09 +0000 UTC - event for calico-node-xnkg8: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:50:09 +0000 UTC - event for calico-node-xnkg8: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-xnkg8 to capz-conf-e0y1lq-control-plane-2k75s
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:50:18 +0000 UTC - event for calico-node-xnkg8: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Created: Created container upgrade-ipam
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:50:18 +0000 UTC - event for calico-node-xnkg8: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 8.337580489s (8.33758859s including waiting)
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:50:19 +0000 UTC - event for calico-node-xnkg8: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Started: Started container upgrade-ipam
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:50:21 +0000 UTC - event for calico-node-xnkg8: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:50:21 +0000 UTC - event for calico-node-xnkg8: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Created: Created container install-cni
Nov 23 16:05:14.096: INFO: At 2022-11-23 15:50:21 +0000 UTC - event for calico-node-xnkg8: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Started: Started container install-cni
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:24 +0000 UTC - event for calico-kube-controllers-657b584867-djfgq: {kubelet capz-conf-e0y1lq-control-plane-2k75s} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "7be70e3b5678c3aea5c1f384b240a6ae38041d05d50c6b7f8670a3ee5ca1c12a": 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 23 16:05:14.097: INFO: At 2022-11-23 15:50:24 +0000 UTC - event for calico-kube-controllers-657b584867-djfgq: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-djfgq to capz-conf-e0y1lq-control-plane-2k75s
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:24 +0000 UTC - event for calico-node-xnkg8: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:24 +0000 UTC - event for coredns-787d4945fb-789pf: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-789pf to capz-conf-e0y1lq-control-plane-2k75s
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:24 +0000 UTC - event for coredns-787d4945fb-ntnmt: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-ntnmt to capz-conf-e0y1lq-control-plane-2k75s
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:24 +0000 UTC - event for metrics-server-c9574f845-c5wk2: {kubelet capz-conf-e0y1lq-control-plane-2k75s} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "34ad0b750b0456e5c1dad9560a92928329ee47233e8b41f7cd9b3ff90e8eac30": 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 23 16:05:14.097: INFO: At 2022-11-23 15:50:24 +0000 UTC - event for metrics-server-c9574f845-c5wk2: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-c5wk2 to capz-conf-e0y1lq-control-plane-2k75s
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:25 +0000 UTC - event for coredns-787d4945fb-789pf: {kubelet capz-conf-e0y1lq-control-plane-2k75s} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "6c3bfc0f7d9e349ea4ac0dd06bf113012394595a6dbd9982707dcd1810882c51": 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 23 16:05:14.097: INFO: At 2022-11-23 15:50:25 +0000 UTC - event for coredns-787d4945fb-ntnmt: {kubelet capz-conf-e0y1lq-control-plane-2k75s} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "a823d748265cd94987b3d54d18396919145278f2cdad9bc9a1b45540167c14f3": 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 23 16:05:14.097: INFO: At 2022-11-23 15:50:33 +0000 UTC - event for calico-node-xnkg8: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 8.964313885s (8.964321185s including waiting)
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:33 +0000 UTC - event for calico-node-xnkg8: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Created: Created container calico-node
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:33 +0000 UTC - event for calico-node-xnkg8: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Started: Started container calico-node
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:34 +0000 UTC - event for calico-node-xnkg8: {kubelet capz-conf-e0y1lq-control-plane-2k75s} 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 23 16:05:14.097: INFO: At 2022-11-23 15:50:36 +0000 UTC - event for calico-kube-controllers-657b584867-djfgq: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0"
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:36 +0000 UTC - event for calico-node-xnkg8: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:37 +0000 UTC - event for coredns-787d4945fb-789pf: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Started: Started container coredns
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:37 +0000 UTC - event for coredns-787d4945fb-789pf: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:37 +0000 UTC - event for coredns-787d4945fb-789pf: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Created: Created container coredns
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:37 +0000 UTC - event for coredns-787d4945fb-ntnmt: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:37 +0000 UTC - event for coredns-787d4945fb-ntnmt: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Created: Created container coredns
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:37 +0000 UTC - event for coredns-787d4945fb-ntnmt: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Started: Started container coredns
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:37 +0000 UTC - event for metrics-server-c9574f845-c5wk2: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:38 +0000 UTC - event for coredns-787d4945fb-789pf: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Unhealthy: Readiness probe failed: Get "http://192.168.249.3:8181/ready": dial tcp 192.168.249.3:8181: connect: connection refused
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:38 +0000 UTC - event for coredns-787d4945fb-ntnmt: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Unhealthy: Readiness probe failed: Get "http://192.168.249.2:8181/ready": dial tcp 192.168.249.2:8181: connect: connection refused
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:42 +0000 UTC - event for calico-kube-controllers-657b584867-djfgq: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 6.63642423s (6.636588965s including waiting)
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:43 +0000 UTC - event for calico-kube-controllers-657b584867-djfgq: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Started: Started container calico-kube-controllers
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:43 +0000 UTC - event for calico-kube-controllers-657b584867-djfgq: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Created: Created container calico-kube-controllers
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:47 +0000 UTC - event for metrics-server-c9574f845-c5wk2: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Created: Created container metrics-server
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:47 +0000 UTC - event for metrics-server-c9574f845-c5wk2: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Started: Started container metrics-server
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:50:47 +0000 UTC - event for metrics-server-c9574f845-c5wk2: {kubelet capz-conf-e0y1lq-control-plane-2k75s} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 4.218628293s (9.57443335s including waiting)
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:52:44 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-pbk2s
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:52:44 +0000 UTC - event for calico-node-windows-pbk2s: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-pbk2s to capz-conf-r9lsv
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:52:44 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-lg869
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:52:44 +0000 UTC - event for containerd-logger-lg869: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-lg869 to capz-conf-r9lsv
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:52:44 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-m2z2h
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:52:44 +0000 UTC - event for kube-proxy-windows-m2z2h: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-m2z2h to capz-conf-r9lsv
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:52:45 +0000 UTC - event for kube-proxy-windows-m2z2h: {kubelet capz-conf-r9lsv} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:53:01 +0000 UTC - event for calico-node-windows-pbk2s: {kubelet capz-conf-r9lsv} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:53:01 +0000 UTC - event for containerd-logger-lg869: {kubelet capz-conf-r9lsv} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:53:01 +0000 UTC - event for kube-proxy-windows-m2z2h: {kubelet capz-conf-r9lsv} Created: Created container kube-proxy
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:53:01 +0000 UTC - event for kube-proxy-windows-m2z2h: {kubelet capz-conf-r9lsv} Pulled: Container image "sigwindowstools/kube-proxy:v1.27.0-alpha.0.36_21916415cb33e9-calico-hostprocess" already present on machine
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:53:02 +0000 UTC - event for kube-proxy-windows-m2z2h: {kubelet capz-conf-r9lsv} Started: Started container kube-proxy
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:53:06 +0000 UTC - event for calico-node-windows-pbk2s: {kubelet capz-conf-r9lsv} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 4.6106291s (4.6106291s including waiting)
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:53:06 +0000 UTC - event for calico-node-windows-pbk2s: {kubelet capz-conf-r9lsv} Created: Created container install-cni
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:53:06 +0000 UTC - event for calico-node-windows-pbk2s: {kubelet capz-conf-r9lsv} Started: Started container install-cni
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:53:08 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-fjshf
Nov 23 16:05:14.097: INFO: At 2022-11-23 15:53:08 +0000 UTC - event for csi-proxy-fjshf: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-fjshf to capz-conf-r9lsv
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:09 +0000 UTC - event for csi-proxy-fjshf: {kubelet capz-conf-r9lsv} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:11 +0000 UTC - event for containerd-logger-lg869: {kubelet capz-conf-r9lsv} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 5.455499s (10.0501288s including waiting)
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:12 +0000 UTC - event for calico-node-windows-pbk2s: {kubelet capz-conf-r9lsv} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:18 +0000 UTC - event for containerd-logger-lg869: {kubelet capz-conf-r9lsv} Created: Created container containerd-logger
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:18 +0000 UTC - event for containerd-logger-lg869: {kubelet capz-conf-r9lsv} Started: Started container containerd-logger
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:29 +0000 UTC - event for csi-proxy-fjshf: {kubelet capz-conf-r9lsv} Started: Started container csi-proxy
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:29 +0000 UTC - event for csi-proxy-fjshf: {kubelet capz-conf-r9lsv} Created: Created container csi-proxy
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:29 +0000 UTC - event for csi-proxy-fjshf: {kubelet capz-conf-r9lsv} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 17.380333s (19.8383266s including waiting)
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:33 +0000 UTC - event for calico-node-windows-pbk2s: {kubelet capz-conf-r9lsv} Started: Started container calico-node-startup
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:33 +0000 UTC - event for calico-node-windows-pbk2s: {kubelet capz-conf-r9lsv} Created: Created container calico-node-startup
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:33 +0000 UTC - event for calico-node-windows-pbk2s: {kubelet capz-conf-r9lsv} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:33 +0000 UTC - event for calico-node-windows-pbk2s: {kubelet capz-conf-r9lsv} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 3.8731282s (20.8244654s including waiting)
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:34 +0000 UTC - event for calico-node-windows-pbk2s: {kubelet capz-conf-r9lsv} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 693.5019ms (693.5019ms including waiting)
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:40 +0000 UTC - event for calico-node-windows-pbk2s: {kubelet capz-conf-r9lsv} Created: Created container calico-node-felix
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:40 +0000 UTC - event for calico-node-windows-pbk2s: {kubelet capz-conf-r9lsv} Started: Started container calico-node-felix
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:57 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-cfkkl
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:57 +0000 UTC - event for calico-node-windows-cfkkl: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-cfkkl to capz-conf-5f845
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:57 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-9845c
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:57 +0000 UTC - event for containerd-logger-9845c: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-9845c to capz-conf-5f845
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:57 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-2lkdl
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:57 +0000 UTC - event for kube-proxy-windows-2lkdl: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-2lkdl to capz-conf-5f845
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:59 +0000 UTC - event for containerd-logger-9845c: {kubelet capz-conf-5f845} FailedMount: MountVolume.SetUp failed for volume "containerd-logger-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:53:59 +0000 UTC - event for kube-proxy-windows-2lkdl: {kubelet capz-conf-5f845} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:01 +0000 UTC - event for calico-node-windows-pbk2s: {kubelet capz-conf-r9lsv} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 679.4747ms (679.4747ms including waiting)
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:17 +0000 UTC - event for calico-node-windows-cfkkl: {kubelet capz-conf-5f845} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:17 +0000 UTC - event for containerd-logger-9845c: {kubelet capz-conf-5f845} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:17 +0000 UTC - event for kube-proxy-windows-2lkdl: {kubelet capz-conf-5f845} Pulled: Container image "sigwindowstools/kube-proxy:v1.27.0-alpha.0.36_21916415cb33e9-calico-hostprocess" already present on machine
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:18 +0000 UTC - event for kube-proxy-windows-2lkdl: {kubelet capz-conf-5f845} Created: Created container kube-proxy
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:18 +0000 UTC - event for kube-proxy-windows-2lkdl: {kubelet capz-conf-5f845} Started: Started container kube-proxy
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:22 +0000 UTC - event for calico-node-windows-cfkkl: {kubelet capz-conf-5f845} Created: Created container install-cni
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:22 +0000 UTC - event for calico-node-windows-cfkkl: {kubelet capz-conf-5f845} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 4.8780083s (4.8780613s including waiting)
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:23 +0000 UTC - event for calico-node-windows-cfkkl: {kubelet capz-conf-5f845} Started: Started container install-cni
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:25 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-jmblk
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:25 +0000 UTC - event for csi-proxy-jmblk: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-jmblk to capz-conf-5f845
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:25 +0000 UTC - event for csi-proxy-jmblk: {kubelet capz-conf-5f845} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:28 +0000 UTC - event for calico-node-windows-cfkkl: {kubelet capz-conf-5f845} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:28 +0000 UTC - event for containerd-logger-9845c: {kubelet capz-conf-5f845} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 5.8267877s (10.6918121s including waiting)
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:38 +0000 UTC - event for containerd-logger-9845c: {kubelet capz-conf-5f845} Started: Started container containerd-logger
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:38 +0000 UTC - event for containerd-logger-9845c: {kubelet capz-conf-5f845} Created: Created container containerd-logger
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:48 +0000 UTC - event for csi-proxy-jmblk: {kubelet capz-conf-5f845} Created: Created container csi-proxy
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:48 +0000 UTC - event for csi-proxy-jmblk: {kubelet capz-conf-5f845} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 19.5482941s (22.2966193s including waiting)
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:48 +0000 UTC - event for csi-proxy-jmblk: {kubelet capz-conf-5f845} Started: Started container csi-proxy
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:52 +0000 UTC - event for calico-node-windows-cfkkl: {kubelet capz-conf-5f845} Started: Started container calico-node-startup
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:52 +0000 UTC - event for calico-node-windows-cfkkl: {kubelet capz-conf-5f845} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 3.9324508s (23.7295026s including waiting)
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:52 +0000 UTC - event for calico-node-windows-cfkkl: {kubelet capz-conf-5f845} Created: Created container calico-node-startup
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:52 +0000 UTC - event for calico-node-windows-cfkkl: {kubelet capz-conf-5f845} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:54:53 +0000 UTC - event for calico-node-windows-cfkkl: {kubelet capz-conf-5f845} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 674.169ms (674.169ms including waiting)
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:55:00 +0000 UTC - event for calico-node-windows-cfkkl: {kubelet capz-conf-5f845} Created: Created container calico-node-felix
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:55:00 +0000 UTC - event for calico-node-windows-cfkkl: {kubelet capz-conf-5f845} Started: Started container calico-node-felix
Nov 23 16:05:14.098: INFO: At 2022-11-23 15:55:22 +0000 UTC - event for calico-node-windows-cfkkl: {kubelet capz-conf-5f845} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 675.8326ms (675.8326ms including waiting)
Nov 23 16:05:14.259: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 23 16:05:14.260: INFO: calico-kube-controllers-657b584867-djfgq capz-conf-e0y1lq-control-plane-2k75s Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:24 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:44 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:44 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:24 +0000 UTC }]
Nov 23 16:05:14.260: INFO: calico-node-windows-cfkkl capz-conf-5f845 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:54:28 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:55:30 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:55:30 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:57 +0000 UTC }]
Nov 23 16:05:14.260: INFO: calico-node-windows-pbk2s capz-conf-r9lsv Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:12 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:54:07 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:54:07 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:52:44 +0000 UTC }]
Nov 23 16:05:14.260: INFO: calico-node-xnkg8 capz-conf-e0y1lq-control-plane-2k75s Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:24 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:39 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:39 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:09 +0000 UTC }]
Nov 23 16:05:14.260: INFO: containerd-logger-9845c capz-conf-5f845 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:57 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:54:39 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:54:39 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:57 +0000 UTC }]
Nov 23 16:05:14.260: INFO: containerd-logger-lg869 capz-conf-r9lsv Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:52:44 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:19 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:19 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:52:44 +0000 UTC }]
Nov 23 16:05:14.260: INFO: coredns-787d4945fb-789pf capz-conf-e0y1lq-control-plane-2k75s Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:24 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:44 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:44 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:24 +0000 UTC }]
Nov 23 16:05:14.260: INFO: coredns-787d4945fb-ntnmt capz-conf-e0y1lq-control-plane-2k75s Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:24 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:44 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:44 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:24 +0000 UTC }]
Nov 23 16:05:14.260: INFO: csi-proxy-fjshf capz-conf-r9lsv Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:08 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:30 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:30 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:08 +0000 UTC }]
Nov 23 16:05:14.260: INFO: csi-proxy-jmblk capz-conf-5f845 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:54:25 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:54:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:54:48 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:54:25 +0000 UTC }]
Nov 23 16:05:14.260: INFO: etcd-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:49:40 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:49:50 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:49:50 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:49:40 +0000 UTC }]
Nov 23 16:05:14.260: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:14.260: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:14.260: INFO: kube-proxy-hcv54 capz-conf-e0y1lq-control-plane-2k75s Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:49:43 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:49:50 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:49:50 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:49:43 +0000 UTC }]
Nov 23 16:05:14.260: INFO: kube-proxy-windows-2lkdl capz-conf-5f845 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:57 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:54:19 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:54:19 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:57 +0000 UTC }]
Nov 23 16:05:14.260: INFO: kube-proxy-windows-m2z2h capz-conf-r9lsv Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:52:44 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:02 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:53:02 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:52:44 +0000 UTC }]
Nov 23 16:05:14.260: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
Nov 23 16:05:14.260: INFO: metrics-server-c9574f845-c5wk2 capz-conf-e0y1lq-control-plane-2k75s Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:24 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:51:14 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:51:14 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-23 15:50:24 +0000 UTC }]
Nov 23 16:05:14.260: INFO:
Nov 23 16:05:15.368: INFO:
Logging node info for node capz-conf-5f845
Nov 23 16:05:15.487: INFO: Node Info: &Node{ObjectMeta:{capz-conf-5f845 f93a5910-059c-4813-a539-be21674a2825 2136 0 2022-11-23 15:53:57 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D4s_v3 beta.kubernetes.io/os:windows failure-domain.beta.kubernetes.io/region:northeurope failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-5f845 kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:northeurope topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-e0y1lq cluster.x-k8s.io/cluster-namespace:capz-conf-e0y1lq cluster.x-k8s.io/machine:capz-conf-e0y1lq-md-win-7dfdf556f5-xdvml cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-e0y1lq-md-win-7dfdf556f5 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.223.1 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:8d:e0:10 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-23 15:53:57 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-23 15:53:57 +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-23 15:54:24 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-23 15:55:05 +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-23 15:55:19 +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-23 16:05:10 +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-e0y1lq/providers/Microsoft.Compute/virtualMachines/capz-conf-5f845,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-23 16:05:10 +0000 UTC,LastTransitionTime:2022-11-23 15:53:57 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-23 16:05:10 +0000 UTC,LastTransitionTime:2022-11-23 15:53:57 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-23 16:05:10 +0000 UTC,LastTransitionTime:2022-11-23 15:53:57 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-23 16:05:10 +0000 UTC,LastTransitionTime:2022-11-23 15:54:24 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-5f845,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-5f845,SystemUUID:59C0BBFB-4CA1-49FA-9562-9340033ABECE,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.27.0-alpha.0.40+4d1daf69064132-dirty,KubeProxyVersion:v1.27.0-alpha.0.40+4d1daf69064132-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.36_21916415cb33e9-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 23 16:05:15.488: INFO:
Logging kubelet events for node capz-conf-5f845
Nov 23 16:05:15.594: INFO:
Logging pods the kubelet thinks is on node capz-conf-5f845
Nov 23 16:05:15.750: INFO: containerd-logger-9845c started at 2022-11-23 15:53:57 +0000 UTC (0+1 container statuses recorded)
Nov 23 16:05:15.750: INFO: Container containerd-logger ready: true, restart count 0
Nov 23 16:05:15.750: INFO: kube-proxy-windows-2lkdl started at 2022-11-23 15:53:57 +0000 UTC (0+1 container statuses recorded)
Nov 23 16:05:15.750: INFO: Container kube-proxy ready: true, restart count 0
Nov 23 16:05:15.750: INFO: csi-proxy-jmblk started at 2022-11-23 15:54:25 +0000 UTC (0+1 container statuses recorded)
Nov 23 16:05:15.750: INFO: Container csi-proxy ready: true, restart count 0
Nov 23 16:05:15.750: INFO: calico-node-windows-cfkkl started at 2022-11-23 15:53:57 +0000 UTC (1+2 container statuses recorded)
Nov 23 16:05:15.750: INFO: Init container install-cni ready: true, restart count 0
Nov 23 16:05:15.750: INFO: Container calico-node-felix ready: true, restart count 1
Nov 23 16:05:15.750: INFO: Container calico-node-startup ready: true, restart count 0
Nov 23 16:05:16.214: INFO:
Latency metrics for node capz-conf-5f845
Nov 23 16:05:16.214: INFO:
Logging node info for node capz-conf-e0y1lq-control-plane-2k75s
Nov 23 16:05:16.332: INFO: Node Info: &Node{ObjectMeta:{capz-conf-e0y1lq-control-plane-2k75s 628c3cdd-4c2d-4299-98e6-1e2fa19d8c6d 1794 0 2022-11-23 15:49:34 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:northeurope failure-domain.beta.kubernetes.io/zone:northeurope-1 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-e0y1lq-control-plane-2k75s kubernetes.io/os:linux node-role.kubernetes.io/control-plane: node.kubernetes.io/exclude-from-external-load-balancers: node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:northeurope topology.kubernetes.io/zone:northeurope-1] map[cluster.x-k8s.io/cluster-name:capz-conf-e0y1lq cluster.x-k8s.io/cluster-namespace:capz-conf-e0y1lq cluster.x-k8s.io/machine:capz-conf-e0y1lq-control-plane-tsx9h cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-e0y1lq-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.249.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2022-11-23 15:49:34 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kubeadm Update v1 2022-11-23 15:49:38 +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-23 15:50:04 +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-23 15:50:24 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2022-11-23 15:50:34 +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-23 16:01:23 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-e0y1lq/providers/Microsoft.Compute/virtualMachines/capz-conf-e0y1lq-control-plane-2k75s,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-23 15:50:34 +0000 UTC,LastTransitionTime:2022-11-23 15:50:34 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-23 16:01:23 +0000 UTC,LastTransitionTime:2022-11-23 15:49:19 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-23 16:01:23 +0000 UTC,LastTransitionTime:2022-11-23 15:49:19 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-23 16:01:23 +0000 UTC,LastTransitionTime:2022-11-23 15:49:19 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-23 16:01:23 +0000 UTC,LastTransitionTime:2022-11-23 15:50:24 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-e0y1lq-control-plane-2k75s,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:8f7790a7e0c1489c9f72d5733aa59141,SystemUUID:ddc6d6d8-700e-f641-b193-830780604512,BootID:a056339e-3f72-4bb6-9983-aca04b69f22e,KernelVersion:5.4.0-1091-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.40+4d1daf69064132,KubeProxyVersion:v1.27.0-alpha.0.40+4d1daf69064132,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[docker.io/calico/cni@sha256:914823d144204288f881e49b93b6852febfe669074cd4e2a782860981615f521 docker.io/calico/cni:v3.23.0],SizeBytes:110494683,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:b83c1d70989e1fe87583607bf5aee1ee34e52773d4755b95f5cf5a451962f3a4 registry.k8s.io/etcd:3.5.5-0],SizeBytes:102417044,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:6f72b851544986cb0921b53ea655ec04c36131248f16d4ad110cb3ca0c369dc1 registry.k8s.io/etcd:3.5.4-0],SizeBytes:102157811,},ContainerImage{Names:[docker.io/calico/node@sha256:4763820ecb4d8e82483a2ffabfec7fcded9603318692df210a778d223a4d7474 docker.io/calico/node:v3.23.0],SizeBytes:71573794,},ContainerImage{Names:[docker.io/calico/kube-controllers@sha256:78bc199299f966b0694dc4044501aee2d7ebd6862b2b0a00bca3ee8d3813c82f docker.io/calico/kube-controllers:v3.23.0],SizeBytes:56343954,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-apiserver@sha256:6b79ea2fa8e882423bd4c814a88db44dfa8debf9c27a8aad859f5bd66b50af06 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.36_21916415cb33e9],SizeBytes:35317315,},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:f50d7969c35f81df11712b5ed084f31b0cba946811b5a85328506acf8165bc45 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.36_21916415cb33e9],SizeBytes:32243480,},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:810add88c862cffdf96a974b5efaaa70a7763380d6538df5b4e765cf7c2dc332 gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.36_21916415cb33e9],SizeBytes:21534326,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:61c248452fae40ef2e8b7cc1ea0065fa0a1047582fd3bccc37f04baa1cafc5b2 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.40_4d1daf69064132],SizeBytes:21532624,},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:11bf7a931a4541fcdf405344d125d796d0db16b4cb33cace2962d4e4902388ae gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.36_21916415cb33e9],SizeBytes:17482757,},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 23 16:05:16.333: INFO:
Logging kubelet events for node capz-conf-e0y1lq-control-plane-2k75s
Nov 23 16:05:16.439: INFO:
Logging pods the kubelet thinks is on node capz-conf-e0y1lq-control-plane-2k75s
Nov 23 16:05:16.653: INFO: metrics-server-c9574f845-c5wk2 started at 2022-11-23 15:50:24 +0000 UTC (0+1 container statuses recorded)
Nov 23 16:05:16.653: INFO: Container metrics-server ready: true, restart count 0
Nov 23 16:05:16.653: INFO: kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s started at <nil> (0+0 container statuses recorded)
Nov 23 16:05:16.653: INFO: etcd-capz-conf-e0y1lq-control-plane-2k75s started at 2022-11-23 15:49:40 +0000 UTC (0+1 container statuses recorded)
Nov 23 16:05:16.653: INFO: Container etcd ready: true, restart count 0
Nov 23 16:05:16.653: INFO: calico-node-xnkg8 started at 2022-11-23 15:50:09 +0000 UTC (2+1 container statuses recorded)
Nov 23 16:05:16.653: INFO: Init container upgrade-ipam ready: true, restart count 0
Nov 23 16:05:16.653: INFO: Init container install-cni ready: true, restart count 0
Nov 23 16:05:16.653: INFO: Container calico-node ready: true, restart count 0
Nov 23 16:05:16.653: INFO: coredns-787d4945fb-ntnmt started at 2022-11-23 15:50:24 +0000 UTC (0+1 container statuses recorded)
Nov 23 16:05:16.653: INFO: Container coredns ready: true, restart count 0
Nov 23 16:05:16.653: INFO: calico-kube-controllers-657b584867-djfgq started at 2022-11-23 15:50:24 +0000 UTC (0+1 container statuses recorded)
Nov 23 16:05:16.653: INFO: Container calico-kube-controllers ready: true, restart count 0
Nov 23 16:05:16.653: INFO: coredns-787d4945fb-789pf started at 2022-11-23 15:50:24 +0000 UTC (0+1 container statuses recorded)
Nov 23 16:05:16.653: INFO: Container coredns ready: true, restart count 0
Nov 23 16:05:16.653: INFO: kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s started at <nil> (0+0 container statuses recorded)
Nov 23 16:05:16.653: INFO: kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s started at <nil> (0+0 container statuses recorded)
Nov 23 16:05:16.653: INFO: kube-proxy-hcv54 started at 2022-11-23 15:49:43 +0000 UTC (0+1 container statuses recorded)
Nov 23 16:05:16.653: INFO: Container kube-proxy ready: true, restart count 0
Nov 23 16:05:17.048: INFO:
Latency metrics for node capz-conf-e0y1lq-control-plane-2k75s
Nov 23 16:05:17.048: INFO:
Logging node info for node capz-conf-r9lsv
Nov 23 16:05:17.157: INFO: Node Info: &Node{ObjectMeta:{capz-conf-r9lsv b5f66864-6b84-4f76-8425-0d73eeb9e2c0 2025 0 2022-11-23 15:52:44 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D4s_v3 beta.kubernetes.io/os:windows failure-domain.beta.kubernetes.io/region:northeurope failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-r9lsv kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:northeurope topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-e0y1lq cluster.x-k8s.io/cluster-namespace:capz-conf-e0y1lq cluster.x-k8s.io/machine:capz-conf-e0y1lq-md-win-7dfdf556f5-t8bn2 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-e0y1lq-md-win-7dfdf556f5 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.78.193 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:87:a3:b3 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-23 15:52:44 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-23 15:52:44 +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-23 15:53:08 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-23 15:53:26 +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-23 15:53:58 +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-23 16:03:57 +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-e0y1lq/providers/Microsoft.Compute/virtualMachines/capz-conf-r9lsv,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-23 16:03:57 +0000 UTC,LastTransitionTime:2022-11-23 15:52:44 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-23 16:03:57 +0000 UTC,LastTransitionTime:2022-11-23 15:52:44 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-23 16:03:57 +0000 UTC,LastTransitionTime:2022-11-23 15:52:44 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-23 16:03:57 +0000 UTC,LastTransitionTime:2022-11-23 15:53:08 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-r9lsv,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-r9lsv,SystemUUID:EBB08DB3-6727-449F-8D7C-0EB5E50A621D,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.27.0-alpha.0.40+4d1daf69064132-dirty,KubeProxyVersion:v1.27.0-alpha.0.40+4d1daf69064132-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.36_21916415cb33e9-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 23 16:05:17.157: INFO:
Logging kubelet events for node capz-conf-r9lsv
Nov 23 16:05:17.262: INFO:
Logging pods the kubelet thinks is on node capz-conf-r9lsv
Nov 23 16:05:17.384: INFO: kube-proxy-windows-m2z2h started at 2022-11-23 15:52:44 +0000 UTC (0+1 container statuses recorded)
Nov 23 16:05:17.384: INFO: Container kube-proxy ready: true, restart count 0
Nov 23 16:05:17.384: INFO: containerd-logger-lg869 started at 2022-11-23 15:52:44 +0000 UTC (0+1 container statuses recorded)
Nov 23 16:05:17.384: INFO: Container containerd-logger ready: true, restart count 0
Nov 23 16:05:17.384: INFO: calico-node-windows-pbk2s started at 2022-11-23 15:52:44 +0000 UTC (1+2 container statuses recorded)
Nov 23 16:05:17.384: INFO: Init container install-cni ready: true, restart count 0
Nov 23 16:05:17.384: INFO: Container calico-node-felix ready: true, restart count 1
Nov 23 16:05:17.384: INFO: Container calico-node-startup ready: true, restart count 0
Nov 23 16:05:17.384: INFO: csi-proxy-fjshf started at 2022-11-23 15:53:08 +0000 UTC (0+1 container statuses recorded)
Nov 23 16:05:17.384: INFO: Container csi-proxy ready: true, restart count 0
Nov 23 16:05:17.776: INFO:
Latency metrics for node capz-conf-r9lsv
Nov 23 16:05:17.928: INFO: Running kubectl logs on non-ready containers in kube-system
Nov 23 16:05:18.304: INFO: Failed to get logs of pod kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s)
Nov 23 16:05:18.304: INFO: Logs of kube-system/kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s:kube-apiserver on node capz-conf-e0y1lq-control-plane-2k75s
Nov 23 16:05:18.304: INFO: : STARTLOG
ENDLOG for container kube-system:kube-apiserver-capz-conf-e0y1lq-control-plane-2k75s:kube-apiserver
Nov 23 16:05:18.704: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s)
Nov 23 16:05:18.704: INFO: Logs of kube-system/kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s:kube-controller-manager on node capz-conf-e0y1lq-control-plane-2k75s
Nov 23 16:05:18.704: INFO: : STARTLOG
ENDLOG for container kube-system:kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s:kube-controller-manager
Nov 23 16:05:19.104: INFO: Failed to get logs of pod kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s)
Nov 23 16:05:19.104: INFO: Logs of kube-system/kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s:kube-scheduler on node capz-conf-e0y1lq-control-plane-2k75s
Nov 23 16:05:19.104: INFO: : STARTLOG
ENDLOG for container kube-system:kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s:kube-scheduler
Nov 23 16:05:19.104: 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-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
kube-controller-manager-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s Pending []
kube-scheduler-capz-conf-e0y1lq-control-plane-2k75s capz-conf-e0y1lq-control-plane-2k75s 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
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e suite report
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
capz-e2e Conformance Tests conformance-tests
capz-e2e Running the Cluster API E2E tests API Version Upgrade upgrade from v1alpha4 to v1beta1, and scale workload clusters created in v1alpha4 Should create a management cluster and then upgrade all the providers
capz-e2e Running the Cluster API E2E tests Running KCP upgrade in a HA cluster [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Running KCP upgrade in a HA cluster using scale in rollout [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Running the MachineDeployment rollout spec Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
capz-e2e Running the Cluster API E2E tests Running the quick-start spec Should create a workload cluster
capz-e2e Running the Cluster API E2E tests Running the self-hosted spec Should pivot the bootstrap cluster to a self-hosted cluster
capz-e2e Running the Cluster API E2E tests Running the workload cluster upgrade spec [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Should successfully exercise machine pools Should successfully create a cluster with machine pool machines
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger machine deployment remediation
capz-e2e Running the Cluster API E2E tests Should successfully scale out and scale in a MachineDeployment Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count
capz-e2e Running the Cluster API E2E tests Should successfully set and use node drain timeout A node should be forcefully removed if it cannot be drained in time
capz-e2e Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] with a single control plane node and 1 node
capz-e2e Workload cluster creation Creating a VMSS cluster [REQUIRED] with a single control plane node and an AzureMachinePool with 2 Linux and 2 Windows worker nodes
capz-e2e Workload cluster creation Creating a cluster that uses the external cloud provider and external azurediskcsi driver [OPTIONAL] with a 1 control plane nodes and 2 worker nodes
capz-e2e Workload cluster creation Creating a dual-stack cluster [OPTIONAL] With dual-stack worker node
capz-e2e Workload cluster creation Creating a highly available cluster [REQUIRED] With 3 control-plane nodes and 2 Linux and 2 Windows worker nodes
capz-e2e Workload cluster creation Creating a ipv6 control-plane cluster [REQUIRED] With ipv6 worker node
capz-e2e Workload cluster creation Creating a private cluster [OPTIONAL] Creates a public management cluster in a custom vnet
capz-e2e Workload cluster creation Creating an AKS cluster [EXPERIMENTAL][Managed Kubernetes] with a single control plane node and 1 node
capz-e2e Workload cluster creation Creating clusters using clusterclass [OPTIONAL] with a single control plane node, one linux worker node, and one windows worker node
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=external CCM=external AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with intree cloud provider
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=external CCM=internal AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with intree cloud provider
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=internal CCM=internal AzureDiskCSIMigration=false: upgrade to v1.23 should create volumes dynamically with intree cloud provider