PR #112923 pull-kubernetes-e2e-capz-windows-containerd #1592095194654707712
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | pohly: e2e: ginkgo timeouts: use context provided by ginkgo |
| Result | SUCCESS |
| Tests | 4 failed / 6 succeeded |
| Started | |
| Elapsed | 1h5m |
| Revision | 04d3800d5f962cfd7879a41cafab90468a209c51 |
| Refs |
112923 |
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({0x7fa8885138f0, 0xc002f24040})
test/e2e/e2e.go:249 +0x5bf
k8s.io/kubernetes/test/e2e.glob..func1({0x7fa8885138f0, 0xc002f24040})
test/e2e/e2e.go:81 +0xaa
reflect.Value.call({0x6856240?, 0x78af028?, 0x0?}, {0x75d139a, 0x4}, {0xc0000b3f38, 0x1, 0x0?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x6856240?, 0x78af028?, 0x0?}, {0xc0000b3f38?, 0x0?, 0x0?})
/usr/local/go/src/reflect/value.go:368 +0xbc
[SynchronizedBeforeSuite] TOP-LEVEL
test/e2e/e2e.go:77
Nov 14 10:46:10.220: INFO: >>> kubeConfig: /tmp/kubeconfig
Nov 14 10:46:10.222: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Nov 14 10:46:10.399: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Nov 14 10:46:10.536: INFO: The status of Pod calico-node-windows-hstrc is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:10.536: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:10.536: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:10.536: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:10.536: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Nov 14 10:46:10.536: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:10.536: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:10.536: INFO: calico-node-windows-hstrc capz-conf-9z748 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:17 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:07 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:07 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:39 +0000 UTC }]
Nov 14 10:46:10.536: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:10.537: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:10.537: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:10.537: INFO:
Nov 14 10:46:12.666: INFO: The status of Pod calico-node-windows-hstrc is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:12.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:12.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:12.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:12.666: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Nov 14 10:46:12.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:12.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:12.666: INFO: calico-node-windows-hstrc capz-conf-9z748 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:17 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:07 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:07 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:39 +0000 UTC }]
Nov 14 10:46:12.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:12.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:12.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:12.666: INFO:
Nov 14 10:46:14.703: INFO: The status of Pod calico-node-windows-hstrc is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:14.703: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:14.703: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:14.703: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:14.703: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Nov 14 10:46:14.703: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:14.703: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:14.703: INFO: calico-node-windows-hstrc capz-conf-9z748 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:17 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:07 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:07 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:39 +0000 UTC }]
Nov 14 10:46:14.703: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:14.703: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:14.703: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:14.703: INFO:
Nov 14 10:46:16.664: INFO: The status of Pod calico-node-windows-hstrc is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:16.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:16.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:16.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:16.664: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Nov 14 10:46:16.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:16.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:16.665: INFO: calico-node-windows-hstrc capz-conf-9z748 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:17 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:07 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:07 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:39 +0000 UTC }]
Nov 14 10:46:16.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:16.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:16.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:16.665: INFO:
Nov 14 10:46:18.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:18.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:18.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:18.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Nov 14 10:46:18.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:18.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:18.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:18.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:18.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:18.663: INFO:
Nov 14 10:46:20.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:20.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:20.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:20.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Nov 14 10:46:20.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:20.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:20.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:20.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:20.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:20.669: INFO:
Nov 14 10:46:22.674: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:22.674: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:22.674: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:22.674: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Nov 14 10:46:22.674: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:22.674: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:22.674: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:22.674: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:22.674: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:22.674: INFO:
Nov 14 10:46:24.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:24.665: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:24.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:24.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Nov 14 10:46:24.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:24.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:24.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:24.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:24.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:24.665: INFO:
Nov 14 10:46:26.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:26.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:26.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:26.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Nov 14 10:46:26.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:26.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:26.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:26.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:26.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:26.664: INFO:
Nov 14 10:46:28.673: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:28.673: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:28.673: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:28.673: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Nov 14 10:46:28.673: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:28.673: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:28.673: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:28.673: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:28.673: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:28.673: INFO:
Nov 14 10:46:30.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:30.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:30.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:30.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Nov 14 10:46:30.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:30.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:30.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:30.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:30.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:30.663: INFO:
Nov 14 10:46:32.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:32.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:32.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:32.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Nov 14 10:46:32.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:32.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:32.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:32.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:32.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:32.662: INFO:
Nov 14 10:46:34.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:34.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:34.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:34.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Nov 14 10:46:34.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:34.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:34.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:34.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:34.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:34.662: INFO:
Nov 14 10:46:36.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:36.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:36.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:36.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Nov 14 10:46:36.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:36.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:36.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:36.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:36.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:36.667: INFO:
Nov 14 10:46:38.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:38.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:38.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:38.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Nov 14 10:46:38.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:38.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:38.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:38.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:38.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:38.663: INFO:
Nov 14 10:46:40.686: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:40.686: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:40.686: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:40.686: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
Nov 14 10:46:40.686: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:40.686: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:40.686: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:40.686: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:40.686: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:40.686: INFO:
Nov 14 10:46:42.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:42.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:42.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:42.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
Nov 14 10:46:42.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:42.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:42.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:42.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:42.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:42.663: INFO:
Nov 14 10:46:44.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:44.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:44.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:44.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
Nov 14 10:46:44.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:44.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:44.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:44.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:44.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:44.662: INFO:
Nov 14 10:46:46.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:46.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:46.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:46.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
Nov 14 10:46:46.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:46.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:46.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:46.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:46.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:46.662: INFO:
Nov 14 10:46:48.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:48.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:48.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:48.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
Nov 14 10:46:48.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:48.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:48.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:48.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:48.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:48.664: INFO:
Nov 14 10:46:50.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:50.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:50.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:50.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
Nov 14 10:46:50.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:50.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:50.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:50.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:50.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:50.663: INFO:
Nov 14 10:46:52.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:52.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:52.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:52.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
Nov 14 10:46:52.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:52.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:52.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:52.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:52.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:52.662: INFO:
Nov 14 10:46:54.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:54.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:54.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:54.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
Nov 14 10:46:54.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:54.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:54.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:54.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:54.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:54.663: INFO:
Nov 14 10:46:56.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:56.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:56.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:56.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
Nov 14 10:46:56.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:56.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:56.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:56.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:56.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:56.663: INFO:
Nov 14 10:46:58.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:58.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:58.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:46:58.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
Nov 14 10:46:58.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:46:58.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:46:58.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:58.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:58.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:46:58.664: INFO:
Nov 14 10:47:00.773: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:00.773: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:00.773: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:00.773: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
Nov 14 10:47:00.773: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:00.773: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:00.773: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:00.773: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:00.773: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:00.773: INFO:
Nov 14 10:47:02.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:02.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:02.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:02.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
Nov 14 10:47:02.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:02.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:02.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:02.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:02.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:02.666: INFO:
Nov 14 10:47:04.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:04.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:04.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:04.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
Nov 14 10:47:04.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:04.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:04.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:04.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:04.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:04.663: INFO:
Nov 14 10:47:06.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:06.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:06.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:06.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
Nov 14 10:47:06.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:06.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:06.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:06.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:06.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:06.663: INFO:
Nov 14 10:47:08.671: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:08.671: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:08.671: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:08.671: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
Nov 14 10:47:08.671: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:08.671: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:08.671: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:08.671: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:08.671: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:08.671: INFO:
Nov 14 10:47:10.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:10.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:10.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:10.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
Nov 14 10:47:10.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:10.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:10.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:10.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:10.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:10.664: INFO:
Nov 14 10:47:12.672: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:12.672: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:12.672: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:12.672: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
Nov 14 10:47:12.672: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:12.672: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:12.672: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:12.672: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:12.672: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:12.672: INFO:
Nov 14 10:47:14.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:14.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:14.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:14.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
Nov 14 10:47:14.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:14.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:14.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:14.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:14.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:14.663: INFO:
Nov 14 10:47:16.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:16.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:16.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:16.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
Nov 14 10:47:16.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:16.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:16.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:16.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:16.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:16.664: INFO:
Nov 14 10:47:18.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:18.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:18.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:18.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
Nov 14 10:47:18.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:18.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:18.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:18.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:18.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:18.663: INFO:
Nov 14 10:47:20.675: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:20.675: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:20.675: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:20.675: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
Nov 14 10:47:20.675: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:20.675: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:20.675: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:20.675: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:20.675: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:20.675: INFO:
Nov 14 10:47:22.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:22.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:22.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:22.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
Nov 14 10:47:22.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:22.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:22.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:22.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:22.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:22.663: INFO:
Nov 14 10:47:24.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:24.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:24.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:24.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
Nov 14 10:47:24.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:24.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:24.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:24.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:24.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:24.663: INFO:
Nov 14 10:47:26.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:26.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:26.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:26.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
Nov 14 10:47:26.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:26.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:26.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:26.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:26.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:26.664: INFO:
Nov 14 10:47:28.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:28.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:28.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:28.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
Nov 14 10:47:28.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:28.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:28.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:28.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:28.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:28.666: INFO:
Nov 14 10:47:30.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:30.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:30.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:30.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
Nov 14 10:47:30.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:30.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:30.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:30.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:30.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:30.663: INFO:
Nov 14 10:47:32.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:32.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:32.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:32.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
Nov 14 10:47:32.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:32.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:32.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:32.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:32.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:32.663: INFO:
Nov 14 10:47:34.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:34.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:34.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:34.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
Nov 14 10:47:34.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:34.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:34.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:34.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:34.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:34.662: INFO:
Nov 14 10:47:36.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:36.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:36.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:36.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
Nov 14 10:47:36.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:36.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:36.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:36.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:36.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:36.664: INFO:
Nov 14 10:47:38.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:38.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:38.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:38.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
Nov 14 10:47:38.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:38.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:38.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:38.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:38.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:38.664: INFO:
Nov 14 10:47:40.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:40.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:40.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:40.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
Nov 14 10:47:40.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:40.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:40.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:40.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:40.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:40.663: INFO:
Nov 14 10:47:42.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:42.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:42.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:42.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
Nov 14 10:47:42.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:42.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:42.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:42.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:42.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:42.663: INFO:
Nov 14 10:47:44.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:44.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:44.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:44.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
Nov 14 10:47:44.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:44.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:44.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:44.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:44.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:44.664: INFO:
Nov 14 10:47:46.665: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:46.665: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:46.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:46.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
Nov 14 10:47:46.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:46.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:46.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:46.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:46.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:46.665: INFO:
Nov 14 10:47:48.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:48.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:48.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:48.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
Nov 14 10:47:48.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:48.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:48.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:48.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:48.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:48.665: INFO:
Nov 14 10:47:50.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:50.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:50.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:50.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
Nov 14 10:47:50.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:50.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:50.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:50.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:50.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:50.663: INFO:
Nov 14 10:47:52.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:52.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:52.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:52.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
Nov 14 10:47:52.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:52.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:52.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:52.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:52.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:52.663: INFO:
Nov 14 10:47:54.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:54.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:54.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:54.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
Nov 14 10:47:54.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:54.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:54.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:54.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:54.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:54.664: INFO:
Nov 14 10:47:56.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:56.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:56.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:56.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
Nov 14 10:47:56.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:56.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:56.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:56.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:56.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:56.664: INFO:
Nov 14 10:47:58.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:58.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:58.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:47:58.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
Nov 14 10:47:58.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:47:58.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:47:58.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:58.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:58.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:47:58.663: INFO:
Nov 14 10:48:00.671: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:00.671: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:00.671: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:00.671: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
Nov 14 10:48:00.671: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:00.671: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:00.671: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:00.671: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:00.671: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:00.671: INFO:
Nov 14 10:48:02.670: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:02.670: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:02.670: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:02.670: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
Nov 14 10:48:02.670: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:02.670: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:02.670: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:02.670: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:02.670: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:02.670: INFO:
Nov 14 10:48:04.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:04.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:04.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:04.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
Nov 14 10:48:04.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:04.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:04.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:04.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:04.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:04.664: INFO:
Nov 14 10:48:06.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:06.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:06.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:06.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
Nov 14 10:48:06.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:06.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:06.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:06.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:06.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:06.662: INFO:
Nov 14 10:48:08.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:08.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:08.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:08.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
Nov 14 10:48:08.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:08.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:08.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:08.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:08.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:08.663: INFO:
Nov 14 10:48:10.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:10.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:10.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:10.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
Nov 14 10:48:10.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:10.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:10.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:10.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:10.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:10.667: INFO:
Nov 14 10:48:12.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:12.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:12.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:12.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
Nov 14 10:48:12.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:12.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:12.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:12.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:12.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:12.663: INFO:
Nov 14 10:48:14.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:14.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:14.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:14.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
Nov 14 10:48:14.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:14.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:14.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:14.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:14.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:14.664: INFO:
Nov 14 10:48:16.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:16.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:16.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:16.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
Nov 14 10:48:16.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:16.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:16.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:16.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:16.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:16.663: INFO:
Nov 14 10:48:18.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:18.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:18.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:18.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
Nov 14 10:48:18.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:18.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:18.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:18.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:18.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:18.662: INFO:
Nov 14 10:48:20.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:20.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:20.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:20.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
Nov 14 10:48:20.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:20.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:20.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:20.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:20.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:20.663: INFO:
Nov 14 10:48:22.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:22.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:22.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:22.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
Nov 14 10:48:22.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:22.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:22.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:22.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:22.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:22.664: INFO:
Nov 14 10:48:24.665: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:24.665: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:24.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:24.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
Nov 14 10:48:24.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:24.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:24.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:24.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:24.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:24.665: INFO:
Nov 14 10:48:26.671: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:26.671: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:26.671: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:26.671: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
Nov 14 10:48:26.671: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:26.671: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:26.671: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:26.671: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:26.671: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:26.671: INFO:
Nov 14 10:48:28.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:28.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:28.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:28.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
Nov 14 10:48:28.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:28.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:28.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:28.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:28.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:28.667: INFO:
Nov 14 10:48:30.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:30.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:30.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:30.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
Nov 14 10:48:30.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:30.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:30.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:30.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:30.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:30.668: INFO:
Nov 14 10:48:32.665: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:32.665: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:32.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:32.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
Nov 14 10:48:32.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:32.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:32.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:32.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:32.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:32.665: INFO:
Nov 14 10:48:34.665: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:34.665: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:34.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:34.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
Nov 14 10:48:34.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:34.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:34.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:34.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:34.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:34.665: INFO:
Nov 14 10:48:36.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:36.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:36.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:36.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
Nov 14 10:48:36.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:36.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:36.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:36.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:36.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:36.664: INFO:
Nov 14 10:48:38.670: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:38.670: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:38.670: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:38.670: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
Nov 14 10:48:38.670: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:38.670: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:38.670: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:38.670: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:38.670: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:38.670: INFO:
Nov 14 10:48:40.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:40.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:40.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:40.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
Nov 14 10:48:40.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:40.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:40.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:40.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:40.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:40.663: INFO:
Nov 14 10:48:42.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:42.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:42.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:42.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
Nov 14 10:48:42.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:42.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:42.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:42.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:42.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:42.662: INFO:
Nov 14 10:48:44.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:44.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:44.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:44.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
Nov 14 10:48:44.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:44.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:44.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:44.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:44.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:44.663: INFO:
Nov 14 10:48:46.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:46.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:46.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:46.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
Nov 14 10:48:46.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:46.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:46.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:46.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:46.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:46.664: INFO:
Nov 14 10:48:48.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:48.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:48.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:48.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
Nov 14 10:48:48.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:48.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:48.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:48.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:48.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:48.664: INFO:
Nov 14 10:48:50.665: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:50.665: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:50.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:50.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
Nov 14 10:48:50.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:50.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:50.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:50.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:50.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:50.665: INFO:
Nov 14 10:48:52.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:52.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:52.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:52.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
Nov 14 10:48:52.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:52.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:52.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:52.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:52.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:52.664: INFO:
Nov 14 10:48:54.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:54.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:54.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:54.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
Nov 14 10:48:54.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:54.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:54.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:54.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:54.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:54.662: INFO:
Nov 14 10:48:56.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:56.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:56.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:56.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
Nov 14 10:48:56.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:56.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:56.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:56.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:56.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:56.662: INFO:
Nov 14 10:48:58.673: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:58.673: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:58.673: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:48:58.673: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
Nov 14 10:48:58.673: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:48:58.673: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:48:58.673: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:58.673: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:58.673: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:48:58.673: INFO:
Nov 14 10:49:00.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:00.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:00.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:00.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
Nov 14 10:49:00.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:00.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:00.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:00.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:00.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:00.662: INFO:
Nov 14 10:49:02.677: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:02.677: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:02.677: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:02.677: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
Nov 14 10:49:02.677: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:02.677: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:02.677: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:02.677: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:02.677: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:02.677: INFO:
Nov 14 10:49:04.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:04.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:04.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:04.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
Nov 14 10:49:04.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:04.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:04.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:04.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:04.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:04.662: INFO:
Nov 14 10:49:06.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:06.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:06.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:06.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
Nov 14 10:49:06.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:06.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:06.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:06.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:06.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:06.662: INFO:
Nov 14 10:49:08.698: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:08.698: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:08.698: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:08.698: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
Nov 14 10:49:08.698: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:08.698: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:08.698: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:08.698: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:08.698: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:08.698: INFO:
Nov 14 10:49:10.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:10.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:10.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:10.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
Nov 14 10:49:10.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:10.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:10.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:10.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:10.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:10.666: INFO:
Nov 14 10:49:12.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:12.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:12.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:12.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
Nov 14 10:49:12.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:12.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:12.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:12.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:12.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:12.663: INFO:
Nov 14 10:49:14.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:14.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:14.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:14.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
Nov 14 10:49:14.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:14.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:14.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:14.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:14.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:14.663: INFO:
Nov 14 10:49:16.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:16.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:16.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:16.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
Nov 14 10:49:16.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:16.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:16.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:16.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:16.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:16.663: INFO:
Nov 14 10:49:18.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:18.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:18.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:18.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
Nov 14 10:49:18.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:18.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:18.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:18.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:18.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:18.663: INFO:
Nov 14 10:49:20.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:20.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:20.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:20.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
Nov 14 10:49:20.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:20.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:20.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:20.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:20.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:20.662: INFO:
Nov 14 10:49:22.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:22.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:22.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:22.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
Nov 14 10:49:22.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:22.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:22.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:22.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:22.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:22.662: INFO:
Nov 14 10:49:24.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:24.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:24.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:24.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
Nov 14 10:49:24.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:24.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:24.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:24.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:24.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:24.663: INFO:
Nov 14 10:49:26.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:26.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:26.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:26.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
Nov 14 10:49:26.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:26.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:26.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:26.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:26.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:26.662: INFO:
Nov 14 10:49:28.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:28.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:28.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:28.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
Nov 14 10:49:28.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:28.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:28.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:28.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:28.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:28.664: INFO:
Nov 14 10:49:30.775: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:30.775: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:30.775: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:30.775: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
Nov 14 10:49:30.775: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:30.775: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:30.775: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:30.775: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:30.775: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:30.775: INFO:
Nov 14 10:49:32.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:32.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:32.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:32.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
Nov 14 10:49:32.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:32.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:32.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:32.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:32.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:32.663: INFO:
Nov 14 10:49:34.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:34.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:34.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:34.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
Nov 14 10:49:34.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:34.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:34.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:34.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:34.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:34.663: INFO:
Nov 14 10:49:36.665: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:36.665: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:36.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:36.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
Nov 14 10:49:36.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:36.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:36.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:36.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:36.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:36.665: INFO:
Nov 14 10:49:38.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:38.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:38.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:38.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
Nov 14 10:49:38.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:38.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:38.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:38.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:38.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:38.666: INFO:
Nov 14 10:49:40.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:40.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:40.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:40.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
Nov 14 10:49:40.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:40.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:40.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:40.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:40.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:40.663: INFO:
Nov 14 10:49:42.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:42.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:42.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:42.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
Nov 14 10:49:42.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:42.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:42.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:42.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:42.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:42.663: INFO:
Nov 14 10:49:44.665: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:44.665: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:44.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:44.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
Nov 14 10:49:44.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:44.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:44.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:44.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:44.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:44.665: INFO:
Nov 14 10:49:46.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:46.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:46.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:46.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
Nov 14 10:49:46.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:46.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:46.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:46.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:46.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:46.663: INFO:
Nov 14 10:49:48.661: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:48.661: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:48.661: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:48.661: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
Nov 14 10:49:48.661: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:48.661: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:48.661: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:48.661: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:48.661: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:48.661: INFO:
Nov 14 10:49:50.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:50.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:50.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:50.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
Nov 14 10:49:50.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:50.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:50.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:50.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:50.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:50.663: INFO:
Nov 14 10:49:52.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:52.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:52.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:52.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
Nov 14 10:49:52.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:52.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:52.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:52.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:52.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:52.663: INFO:
Nov 14 10:49:54.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:54.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:54.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:54.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
Nov 14 10:49:54.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:54.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:54.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:54.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:54.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:54.664: INFO:
Nov 14 10:49:56.680: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:56.680: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:56.680: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:56.680: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
Nov 14 10:49:56.680: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:56.680: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:56.680: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:56.680: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:56.680: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:56.680: INFO:
Nov 14 10:49:58.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:58.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:58.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:49:58.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
Nov 14 10:49:58.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:49:58.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:49:58.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:58.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:58.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:49:58.662: INFO:
Nov 14 10:50:00.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:00.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:00.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:00.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
Nov 14 10:50:00.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:00.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:00.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:00.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:00.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:00.663: INFO:
Nov 14 10:50:02.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:02.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:02.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:02.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
Nov 14 10:50:02.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:02.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:02.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:02.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:02.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:02.664: INFO:
Nov 14 10:50:04.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:04.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:04.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:04.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
Nov 14 10:50:04.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:04.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:04.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:04.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:04.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:04.662: INFO:
Nov 14 10:50:06.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:06.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:06.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:06.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
Nov 14 10:50:06.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:06.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:06.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:06.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:06.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:06.662: INFO:
Nov 14 10:50:08.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:08.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:08.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:08.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
Nov 14 10:50:08.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:08.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:08.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:08.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:08.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:08.667: INFO:
Nov 14 10:50:10.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:10.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:10.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:10.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
Nov 14 10:50:10.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:10.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:10.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:10.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:10.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:10.664: INFO:
Nov 14 10:50:12.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:12.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:12.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:12.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
Nov 14 10:50:12.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:12.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:12.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:12.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:12.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:12.663: INFO:
Nov 14 10:50:14.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:14.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:14.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:14.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
Nov 14 10:50:14.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:14.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:14.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:14.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:14.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:14.662: INFO:
Nov 14 10:50:16.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:16.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:16.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:16.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
Nov 14 10:50:16.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:16.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:16.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:16.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:16.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:16.663: INFO:
Nov 14 10:50:18.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:18.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:18.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:18.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
Nov 14 10:50:18.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:18.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:18.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:18.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:18.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:18.663: INFO:
Nov 14 10:50:20.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:20.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:20.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:20.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
Nov 14 10:50:20.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:20.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:20.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:20.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:20.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:20.663: INFO:
Nov 14 10:50:22.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:22.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:22.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:22.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
Nov 14 10:50:22.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:22.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:22.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:22.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:22.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:22.663: INFO:
Nov 14 10:50:24.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:24.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:24.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:24.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
Nov 14 10:50:24.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:24.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:24.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:24.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:24.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:24.664: INFO:
Nov 14 10:50:26.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:26.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:26.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:26.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
Nov 14 10:50:26.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:26.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:26.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:26.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:26.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:26.663: INFO:
Nov 14 10:50:28.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:28.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:28.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:28.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
Nov 14 10:50:28.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:28.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:28.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:28.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:28.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:28.663: INFO:
Nov 14 10:50:30.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:30.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:30.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:30.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
Nov 14 10:50:30.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:30.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:30.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:30.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:30.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:30.662: INFO:
Nov 14 10:50:32.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:32.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:32.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:32.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
Nov 14 10:50:32.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:32.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:32.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:32.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:32.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:32.664: INFO:
Nov 14 10:50:34.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:34.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:34.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:34.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
Nov 14 10:50:34.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:34.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:34.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:34.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:34.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:34.667: INFO:
Nov 14 10:50:36.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:36.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:36.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:36.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
Nov 14 10:50:36.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:36.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:36.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:36.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:36.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:36.662: INFO:
Nov 14 10:50:38.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:38.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:38.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:38.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
Nov 14 10:50:38.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:38.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:38.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:38.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:38.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:38.663: INFO:
Nov 14 10:50:40.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:40.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:40.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:40.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
Nov 14 10:50:40.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:40.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:40.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:40.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:40.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:40.664: INFO:
Nov 14 10:50:42.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:42.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:42.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:42.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
Nov 14 10:50:42.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:42.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:42.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:42.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:42.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:42.663: INFO:
Nov 14 10:50:44.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:44.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:44.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:44.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
Nov 14 10:50:44.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:44.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:44.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:44.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:44.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:44.663: INFO:
Nov 14 10:50:46.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:46.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:46.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:46.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
Nov 14 10:50:46.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:46.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:46.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:46.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:46.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:46.669: INFO:
Nov 14 10:50:48.662: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:48.662: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:48.662: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:48.662: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
Nov 14 10:50:48.662: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:48.662: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:48.662: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:48.662: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:48.662: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:48.662: INFO:
Nov 14 10:50:50.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:50.663: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:50.663: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:50.663: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
Nov 14 10:50:50.663: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:50.663: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:50.663: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:50.663: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:50.663: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:50.663: INFO:
Nov 14 10:50:52.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:52.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:52.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:52.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
Nov 14 10:50:52.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:52.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:52.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:52.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:52.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:52.664: INFO:
Nov 14 10:50:54.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:54.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:54.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:54.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
Nov 14 10:50:54.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:54.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:54.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:54.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:54.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:54.664: INFO:
Nov 14 10:50:56.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:56.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:56.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:56.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
Nov 14 10:50:56.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:56.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:56.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:56.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:56.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:56.669: INFO:
Nov 14 10:50:58.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:58.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:58.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:50:58.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
Nov 14 10:50:58.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:50:58.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:50:58.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:58.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:58.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:50:58.669: INFO:
Nov 14 10:51:00.665: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:00.665: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:00.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:00.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
Nov 14 10:51:00.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:00.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:00.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:00.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:00.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:00.665: INFO:
Nov 14 10:51:02.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:02.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:02.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:02.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
Nov 14 10:51:02.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:02.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:02.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:02.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:02.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:02.667: INFO:
Nov 14 10:51:04.665: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:04.665: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:04.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:04.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
Nov 14 10:51:04.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:04.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:04.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:04.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:04.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:04.665: INFO:
Nov 14 10:51:06.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:06.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:06.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:06.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
Nov 14 10:51:06.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:06.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:06.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:06.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:06.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:06.667: INFO:
Nov 14 10:51:08.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:08.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:08.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:08.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
Nov 14 10:51:08.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:08.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:08.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:08.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:08.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:08.668: INFO:
Nov 14 10:51:10.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:10.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:10.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:10.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
Nov 14 10:51:10.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:10.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:10.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:10.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:10.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:10.666: INFO:
Nov 14 10:51:12.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:12.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:12.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:12.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
Nov 14 10:51:12.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:12.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:12.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:12.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:12.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:12.668: INFO:
Nov 14 10:51:14.746: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:14.746: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:14.746: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:14.746: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
Nov 14 10:51:14.746: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:14.746: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:14.746: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:14.746: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:14.746: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:14.746: INFO:
Nov 14 10:51:16.672: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:16.672: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:16.672: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:16.672: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
Nov 14 10:51:16.672: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:16.672: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:16.672: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:16.672: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:16.672: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:16.672: INFO:
Nov 14 10:51:18.676: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:18.676: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:18.676: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:18.676: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
Nov 14 10:51:18.676: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:18.676: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:18.676: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:18.676: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:18.676: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:18.676: INFO:
Nov 14 10:51:20.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:20.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:20.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:20.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
Nov 14 10:51:20.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:20.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:20.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:20.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:20.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:20.669: INFO:
Nov 14 10:51:22.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:22.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:22.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:22.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
Nov 14 10:51:22.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:22.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:22.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:22.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:22.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:22.669: INFO:
Nov 14 10:51:24.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:24.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:24.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:24.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
Nov 14 10:51:24.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:24.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:24.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:24.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:24.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:24.667: INFO:
Nov 14 10:51:26.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:26.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:26.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:26.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
Nov 14 10:51:26.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:26.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:26.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:26.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:26.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:26.667: INFO:
Nov 14 10:51:28.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:28.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:28.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:28.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
Nov 14 10:51:28.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:28.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:28.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:28.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:28.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:28.669: INFO:
Nov 14 10:51:30.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:30.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:30.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:30.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
Nov 14 10:51:30.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:30.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:30.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:30.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:30.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:30.668: INFO:
Nov 14 10:51:32.671: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:32.671: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:32.671: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:32.671: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
Nov 14 10:51:32.671: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:32.671: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:32.671: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:32.671: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:32.671: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:32.671: INFO:
Nov 14 10:51:34.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:34.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:34.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:34.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
Nov 14 10:51:34.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:34.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:34.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:34.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:34.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:34.668: INFO:
Nov 14 10:51:36.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:36.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:36.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:36.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
Nov 14 10:51:36.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:36.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:36.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:36.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:36.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:36.667: INFO:
Nov 14 10:51:38.678: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:38.678: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:38.678: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:38.678: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
Nov 14 10:51:38.678: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:38.678: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:38.678: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:38.678: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:38.678: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:38.678: INFO:
Nov 14 10:51:40.665: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:40.665: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:40.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:40.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
Nov 14 10:51:40.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:40.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:40.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:40.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:40.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:40.665: INFO:
Nov 14 10:51:42.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:42.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:42.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:42.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
Nov 14 10:51:42.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:42.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:42.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:42.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:42.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:42.669: INFO:
Nov 14 10:51:44.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:44.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:44.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:44.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
Nov 14 10:51:44.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:44.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:44.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:44.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:44.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:44.666: INFO:
Nov 14 10:51:46.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:46.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:46.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:46.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
Nov 14 10:51:46.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:46.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:46.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:46.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:46.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:46.666: INFO:
Nov 14 10:51:48.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:48.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:48.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:48.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
Nov 14 10:51:48.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:48.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:48.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:48.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:48.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:48.668: INFO:
Nov 14 10:51:50.670: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:50.670: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:50.670: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:50.670: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
Nov 14 10:51:50.670: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:50.670: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:50.670: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:50.670: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:50.670: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:50.670: INFO:
Nov 14 10:51:52.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:52.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:52.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:52.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
Nov 14 10:51:52.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:52.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:52.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:52.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:52.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:52.669: INFO:
Nov 14 10:51:54.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:54.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:54.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:54.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
Nov 14 10:51:54.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:54.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:54.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:54.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:54.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:54.669: INFO:
Nov 14 10:51:56.783: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:56.783: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:56.783: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:56.783: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
Nov 14 10:51:56.783: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:56.783: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:56.783: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:56.783: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:56.783: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:56.783: INFO:
Nov 14 10:51:58.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:58.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:58.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:51:58.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
Nov 14 10:51:58.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:51:58.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:51:58.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:58.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:58.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:51:58.666: INFO:
Nov 14 10:52:00.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:00.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:00.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:00.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
Nov 14 10:52:00.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:00.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:00.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:00.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:00.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:00.670: INFO:
Nov 14 10:52:02.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:02.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:02.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:02.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
Nov 14 10:52:02.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:02.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:02.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:02.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:02.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:02.669: INFO:
Nov 14 10:52:04.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:04.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:04.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:04.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
Nov 14 10:52:04.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:04.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:04.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:04.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:04.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:04.667: INFO:
Nov 14 10:52:06.664: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:06.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:06.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:06.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
Nov 14 10:52:06.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:06.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:06.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:06.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:06.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:06.664: INFO:
Nov 14 10:52:08.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:08.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:08.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:08.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
Nov 14 10:52:08.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:08.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:08.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:08.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:08.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:08.667: INFO:
Nov 14 10:52:10.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:10.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:10.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:10.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
Nov 14 10:52:10.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:10.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:10.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:10.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:10.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:10.667: INFO:
Nov 14 10:52:12.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:12.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:12.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:12.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
Nov 14 10:52:12.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:12.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:12.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:12.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:12.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:12.668: INFO:
Nov 14 10:52:14.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:14.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:14.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:14.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
Nov 14 10:52:14.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:14.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:14.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:14.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:14.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:14.666: INFO:
Nov 14 10:52:16.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:16.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:16.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:16.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
Nov 14 10:52:16.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:16.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:16.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:16.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:16.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:16.669: INFO:
Nov 14 10:52:18.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:18.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:18.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:18.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
Nov 14 10:52:18.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:18.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:18.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:18.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:18.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:18.667: INFO:
Nov 14 10:52:20.665: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:20.665: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:20.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:20.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
Nov 14 10:52:20.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:20.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:20.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:20.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:20.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:20.665: INFO:
Nov 14 10:52:22.665: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:22.665: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:22.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:22.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
Nov 14 10:52:22.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:22.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:22.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:22.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:22.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:22.665: INFO:
Nov 14 10:52:24.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:24.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:24.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:24.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
Nov 14 10:52:24.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:24.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:24.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:24.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:24.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:24.666: INFO:
Nov 14 10:52:26.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:26.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:26.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:26.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
Nov 14 10:52:26.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:26.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:26.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:26.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:26.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:26.666: INFO:
Nov 14 10:52:28.673: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:28.673: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:28.673: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:28.673: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
Nov 14 10:52:28.673: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:28.673: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:28.673: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:28.673: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:28.673: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:28.673: INFO:
Nov 14 10:52:30.676: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:30.676: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:30.676: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:30.676: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
Nov 14 10:52:30.676: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:30.676: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:30.676: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:30.676: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:30.676: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:30.676: INFO:
Nov 14 10:52:32.670: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:32.670: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:32.670: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:32.670: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
Nov 14 10:52:32.670: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:32.670: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:32.670: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:32.670: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:32.670: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:32.670: INFO:
Nov 14 10:52:34.665: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:34.665: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:34.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:34.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
Nov 14 10:52:34.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:34.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:34.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:34.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:34.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:34.665: INFO:
Nov 14 10:52:36.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:36.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:36.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:36.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
Nov 14 10:52:36.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:36.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:36.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:36.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:36.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:36.669: INFO:
Nov 14 10:52:38.673: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:38.673: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:38.673: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:38.673: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
Nov 14 10:52:38.673: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:38.673: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:38.673: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:38.673: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:38.673: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:38.673: INFO:
Nov 14 10:52:40.679: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:40.679: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:40.679: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:40.679: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
Nov 14 10:52:40.679: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:40.679: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:40.679: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:40.679: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:40.679: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:40.679: INFO:
Nov 14 10:52:42.670: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:42.671: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:42.671: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:42.671: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
Nov 14 10:52:42.671: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:42.671: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:42.671: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:42.671: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:42.671: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:42.671: INFO:
Nov 14 10:52:44.671: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:44.671: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:44.671: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:44.671: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
Nov 14 10:52:44.671: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:44.671: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:44.671: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:44.671: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:44.671: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:44.671: INFO:
Nov 14 10:52:46.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:46.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:46.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:46.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
Nov 14 10:52:46.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:46.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:46.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:46.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:46.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:46.666: INFO:
Nov 14 10:52:48.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:48.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:48.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:48.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
Nov 14 10:52:48.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:48.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:48.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:48.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:48.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:48.666: INFO:
Nov 14 10:52:50.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:50.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:50.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:50.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
Nov 14 10:52:50.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:50.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:50.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:50.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:50.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:50.669: INFO:
Nov 14 10:52:52.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:52.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:52.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:52.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
Nov 14 10:52:52.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:52.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:52.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:52.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:52.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:52.666: INFO:
Nov 14 10:52:54.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:54.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:54.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:54.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
Nov 14 10:52:54.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:54.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:54.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:54.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:54.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:54.667: INFO:
Nov 14 10:52:56.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:56.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:56.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:56.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
Nov 14 10:52:56.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:56.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:56.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:56.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:56.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:56.666: INFO:
Nov 14 10:52:58.782: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:58.782: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:58.782: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:52:58.782: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
Nov 14 10:52:58.782: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:52:58.782: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:52:58.782: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:58.782: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:58.782: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:52:58.782: INFO:
Nov 14 10:53:00.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:00.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:00.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:00.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
Nov 14 10:53:00.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:00.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:00.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:00.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:00.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:00.666: INFO:
Nov 14 10:53:02.676: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:02.676: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:02.676: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:02.676: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
Nov 14 10:53:02.676: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:02.676: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:02.676: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:02.676: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:02.676: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:02.676: INFO:
Nov 14 10:53:04.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:04.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:04.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:04.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
Nov 14 10:53:04.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:04.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:04.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:04.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:04.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:04.666: INFO:
Nov 14 10:53:06.671: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:06.671: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:06.671: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:06.671: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
Nov 14 10:53:06.671: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:06.671: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:06.671: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:06.671: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:06.671: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:06.671: INFO:
Nov 14 10:53:08.670: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:08.670: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:08.670: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:08.670: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
Nov 14 10:53:08.670: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:08.670: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:08.670: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:08.670: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:08.670: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:08.670: INFO:
Nov 14 10:53:10.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:10.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:10.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:10.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
Nov 14 10:53:10.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:10.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:10.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:10.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:10.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:10.669: INFO:
Nov 14 10:53:12.665: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:12.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:12.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:12.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
Nov 14 10:53:12.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:12.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:12.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:12.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:12.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:12.666: INFO:
Nov 14 10:53:14.678: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:14.678: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:14.678: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:14.678: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
Nov 14 10:53:14.678: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:14.678: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:14.678: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:14.678: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:14.678: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:14.678: INFO:
Nov 14 10:53:16.672: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:16.672: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:16.672: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:16.672: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
Nov 14 10:53:16.672: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:16.672: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:16.672: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:16.672: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:16.672: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:16.672: INFO:
Nov 14 10:53:18.670: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:18.670: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:18.670: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:18.670: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
Nov 14 10:53:18.670: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:18.670: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:18.670: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:18.670: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:18.670: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:18.670: INFO:
Nov 14 10:53:20.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:20.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:20.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:20.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
Nov 14 10:53:20.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:20.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:20.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:20.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:20.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:20.667: INFO:
Nov 14 10:53:22.673: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:22.673: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:22.673: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:22.673: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
Nov 14 10:53:22.673: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:22.673: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:22.673: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:22.673: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:22.673: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:22.673: INFO:
Nov 14 10:53:24.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:24.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:24.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:24.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
Nov 14 10:53:24.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:24.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:24.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:24.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:24.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:24.666: INFO:
Nov 14 10:53:26.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:26.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:26.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:26.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
Nov 14 10:53:26.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:26.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:26.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:26.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:26.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:26.667: INFO:
Nov 14 10:53:28.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:28.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:28.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:28.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
Nov 14 10:53:28.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:28.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:28.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:28.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:28.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:28.666: INFO:
Nov 14 10:53:30.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:30.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:30.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:30.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
Nov 14 10:53:30.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:30.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:30.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:30.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:30.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:30.667: INFO:
Nov 14 10:53:32.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:32.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:32.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:32.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
Nov 14 10:53:32.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:32.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:32.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:32.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:32.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:32.668: INFO:
Nov 14 10:53:34.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:34.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:34.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:34.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
Nov 14 10:53:34.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:34.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:34.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:34.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:34.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:34.666: INFO:
Nov 14 10:53:36.674: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:36.674: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:36.674: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:36.674: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
Nov 14 10:53:36.674: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:36.674: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:36.674: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:36.674: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:36.674: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:36.674: INFO:
Nov 14 10:53:38.676: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:38.676: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:38.676: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:38.676: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
Nov 14 10:53:38.676: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:38.676: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:38.676: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:38.676: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:38.676: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:38.676: INFO:
Nov 14 10:53:40.672: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:40.672: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:40.672: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:40.672: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
Nov 14 10:53:40.672: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:40.672: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:40.672: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:40.672: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:40.672: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:40.672: INFO:
Nov 14 10:53:42.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:42.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:42.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:42.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
Nov 14 10:53:42.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:42.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:42.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:42.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:42.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:42.667: INFO:
Nov 14 10:53:44.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:44.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:44.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:44.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
Nov 14 10:53:44.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:44.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:44.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:44.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:44.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:44.668: INFO:
Nov 14 10:53:46.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:46.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:46.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:46.670: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
Nov 14 10:53:46.670: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:46.670: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:46.670: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:46.670: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:46.670: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:46.670: INFO:
Nov 14 10:53:48.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:48.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:48.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:48.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
Nov 14 10:53:48.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:48.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:48.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:48.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:48.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:48.667: INFO:
Nov 14 10:53:50.673: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:50.673: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:50.673: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:50.673: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
Nov 14 10:53:50.673: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:50.673: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:50.673: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:50.673: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:50.673: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:50.673: INFO:
Nov 14 10:53:52.670: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:52.670: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:52.670: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:52.670: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
Nov 14 10:53:52.670: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:52.670: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:52.670: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:52.670: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:52.670: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:52.670: INFO:
Nov 14 10:53:54.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:54.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:54.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:54.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
Nov 14 10:53:54.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:54.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:54.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:54.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:54.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:54.668: INFO:
Nov 14 10:53:56.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:56.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:56.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:56.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
Nov 14 10:53:56.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:56.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:56.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:56.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:56.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:56.668: INFO:
Nov 14 10:53:58.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:58.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:58.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:53:58.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
Nov 14 10:53:58.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:53:58.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:53:58.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:58.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:58.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:53:58.667: INFO:
Nov 14 10:54:00.670: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:00.670: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:00.670: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:00.670: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
Nov 14 10:54:00.670: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:00.670: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:00.670: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:00.670: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:00.670: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:00.670: INFO:
Nov 14 10:54:02.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:02.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:02.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:02.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
Nov 14 10:54:02.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:02.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:02.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:02.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:02.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:02.666: INFO:
Nov 14 10:54:04.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:04.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:04.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:04.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
Nov 14 10:54:04.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:04.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:04.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:04.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:04.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:04.668: INFO:
Nov 14 10:54:06.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:06.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:06.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:06.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
Nov 14 10:54:06.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:06.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:06.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:06.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:06.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:06.666: INFO:
Nov 14 10:54:08.672: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:08.672: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:08.672: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:08.672: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
Nov 14 10:54:08.672: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:08.672: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:08.672: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:08.672: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:08.672: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:08.672: INFO:
Nov 14 10:54:10.673: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:10.673: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:10.673: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:10.673: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
Nov 14 10:54:10.673: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:10.673: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:10.673: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:10.673: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:10.673: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:10.673: INFO:
Nov 14 10:54:12.671: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:12.671: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:12.671: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:12.671: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
Nov 14 10:54:12.671: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:12.671: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:12.671: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:12.671: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:12.671: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:12.671: INFO:
Nov 14 10:54:14.670: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:14.670: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:14.670: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:14.670: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
Nov 14 10:54:14.670: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:14.670: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:14.670: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:14.670: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:14.670: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:14.670: INFO:
Nov 14 10:54:16.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:16.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:16.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:16.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
Nov 14 10:54:16.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:16.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:16.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:16.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:16.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:16.669: INFO:
Nov 14 10:54:18.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:18.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:18.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:18.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
Nov 14 10:54:18.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:18.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:18.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:18.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:18.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:18.667: INFO:
Nov 14 10:54:20.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:20.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:20.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:20.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
Nov 14 10:54:20.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:20.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:20.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:20.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:20.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:20.667: INFO:
Nov 14 10:54:22.670: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:22.670: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:22.670: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:22.670: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
Nov 14 10:54:22.670: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:22.670: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:22.670: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:22.670: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:22.670: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:22.670: INFO:
Nov 14 10:54:24.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:24.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:24.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:24.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
Nov 14 10:54:24.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:24.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:24.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:24.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:24.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:24.667: INFO:
Nov 14 10:54:26.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:26.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:26.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:26.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
Nov 14 10:54:26.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:26.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:26.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:26.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:26.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:26.669: INFO:
Nov 14 10:54:28.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:28.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:28.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:28.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
Nov 14 10:54:28.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:28.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:28.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:28.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:28.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:28.668: INFO:
Nov 14 10:54:30.663: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:30.664: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:30.664: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:30.664: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
Nov 14 10:54:30.664: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:30.664: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:30.664: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:30.664: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:30.664: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:30.664: INFO:
Nov 14 10:54:32.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:32.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:32.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:32.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
Nov 14 10:54:32.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:32.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:32.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:32.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:32.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:32.669: INFO:
Nov 14 10:54:34.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:34.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:34.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:34.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
Nov 14 10:54:34.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:34.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:34.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:34.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:34.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:34.666: INFO:
Nov 14 10:54:36.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:36.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:36.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:36.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
Nov 14 10:54:36.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:36.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:36.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:36.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:36.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:36.667: INFO:
Nov 14 10:54:38.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:38.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:38.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:38.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
Nov 14 10:54:38.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:38.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:38.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:38.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:38.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:38.669: INFO:
Nov 14 10:54:40.670: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:40.670: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:40.670: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:40.670: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
Nov 14 10:54:40.670: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:40.670: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:40.670: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:40.670: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:40.670: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:40.670: INFO:
Nov 14 10:54:42.665: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:42.665: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:42.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:42.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
Nov 14 10:54:42.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:42.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:42.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:42.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:42.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:42.665: INFO:
Nov 14 10:54:44.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:44.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:44.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:44.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
Nov 14 10:54:44.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:44.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:44.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:44.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:44.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:44.668: INFO:
Nov 14 10:54:46.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:46.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:46.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:46.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
Nov 14 10:54:46.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:46.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:46.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:46.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:46.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:46.666: INFO:
Nov 14 10:54:48.670: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:48.670: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:48.670: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:48.670: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
Nov 14 10:54:48.670: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:48.670: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:48.670: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:48.670: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:48.670: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:48.670: INFO:
Nov 14 10:54:50.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:50.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:50.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:50.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
Nov 14 10:54:50.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:50.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:50.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:50.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:50.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:50.667: INFO:
Nov 14 10:54:52.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:52.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:52.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:52.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
Nov 14 10:54:52.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:52.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:52.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:52.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:52.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:52.667: INFO:
Nov 14 10:54:54.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:54.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:54.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:54.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
Nov 14 10:54:54.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:54.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:54.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:54.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:54.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:54.668: INFO:
Nov 14 10:54:56.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:56.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:56.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:56.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
Nov 14 10:54:56.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:56.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:56.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:56.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:56.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:56.669: INFO:
Nov 14 10:54:58.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:58.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:58.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:54:58.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
Nov 14 10:54:58.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:54:58.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:54:58.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:58.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:58.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:54:58.669: INFO:
Nov 14 10:55:00.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:00.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:00.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:00.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
Nov 14 10:55:00.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:00.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:00.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:00.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:00.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:00.667: INFO:
Nov 14 10:55:02.670: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:02.670: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:02.670: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:02.670: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
Nov 14 10:55:02.670: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:02.670: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:02.670: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:02.670: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:02.670: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:02.670: INFO:
Nov 14 10:55:04.786: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:04.786: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:04.786: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:04.786: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
Nov 14 10:55:04.786: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:04.786: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:04.786: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:04.786: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:04.786: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:04.786: INFO:
Nov 14 10:55:06.673: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:06.673: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:06.673: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:06.673: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
Nov 14 10:55:06.673: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:06.673: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:06.673: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:06.673: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:06.673: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:06.673: INFO:
Nov 14 10:55:08.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:08.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:08.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:08.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
Nov 14 10:55:08.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:08.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:08.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:08.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:08.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:08.666: INFO:
Nov 14 10:55:10.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:10.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:10.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:10.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
Nov 14 10:55:10.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:10.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:10.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:10.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:10.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:10.668: INFO:
Nov 14 10:55:12.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:12.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:12.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:12.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
Nov 14 10:55:12.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:12.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:12.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:12.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:12.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:12.667: INFO:
Nov 14 10:55:14.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:14.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:14.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:14.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
Nov 14 10:55:14.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:14.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:14.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:14.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:14.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:14.666: INFO:
Nov 14 10:55:16.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:16.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:16.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:16.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
Nov 14 10:55:16.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:16.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:16.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:16.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:16.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:16.667: INFO:
Nov 14 10:55:18.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:18.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:18.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:18.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
Nov 14 10:55:18.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:18.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:18.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:18.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:18.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:18.668: INFO:
Nov 14 10:55:20.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:20.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:20.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:20.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
Nov 14 10:55:20.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:20.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:20.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:20.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:20.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:20.667: INFO:
Nov 14 10:55:22.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:22.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:22.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:22.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
Nov 14 10:55:22.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:22.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:22.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:22.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:22.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:22.666: INFO:
Nov 14 10:55:24.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:24.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:24.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:24.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
Nov 14 10:55:24.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:24.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:24.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:24.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:24.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:24.667: INFO:
Nov 14 10:55:26.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:26.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:26.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:26.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
Nov 14 10:55:26.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:26.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:26.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:26.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:26.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:26.667: INFO:
Nov 14 10:55:28.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:28.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:28.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:28.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
Nov 14 10:55:28.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:28.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:28.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:28.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:28.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:28.666: INFO:
Nov 14 10:55:30.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:30.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:30.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:30.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
Nov 14 10:55:30.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:30.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:30.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:30.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:30.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:30.668: INFO:
Nov 14 10:55:32.672: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:32.672: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:32.672: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:32.672: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
Nov 14 10:55:32.672: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:32.672: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:32.672: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:32.672: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:32.672: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:32.672: INFO:
Nov 14 10:55:34.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:34.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:34.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:34.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
Nov 14 10:55:34.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:34.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:34.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:34.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:34.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:34.667: INFO:
Nov 14 10:55:36.665: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:36.665: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:36.665: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:36.665: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
Nov 14 10:55:36.665: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:36.665: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:36.665: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:36.665: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:36.665: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:36.665: INFO:
Nov 14 10:55:38.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:38.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:38.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:38.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
Nov 14 10:55:38.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:38.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:38.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:38.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:38.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:38.667: INFO:
Nov 14 10:55:40.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:40.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:40.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:40.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
Nov 14 10:55:40.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:40.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:40.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:40.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:40.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:40.669: INFO:
Nov 14 10:55:42.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:42.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:42.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:42.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
Nov 14 10:55:42.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:42.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:42.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:42.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:42.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:42.666: INFO:
Nov 14 10:55:44.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:44.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:44.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:44.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
Nov 14 10:55:44.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:44.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:44.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:44.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:44.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:44.668: INFO:
Nov 14 10:55:46.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:46.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:46.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:46.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
Nov 14 10:55:46.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:46.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:46.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:46.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:46.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:46.667: INFO:
Nov 14 10:55:48.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:48.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:48.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:48.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
Nov 14 10:55:48.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:48.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:48.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:48.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:48.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:48.667: INFO:
Nov 14 10:55:50.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:50.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:50.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:50.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
Nov 14 10:55:50.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:50.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:50.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:50.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:50.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:50.667: INFO:
Nov 14 10:55:52.672: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:52.672: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:52.672: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:52.672: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
Nov 14 10:55:52.672: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:52.672: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:52.672: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:52.672: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:52.672: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:52.672: INFO:
Nov 14 10:55:54.666: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:54.666: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:54.666: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:54.666: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
Nov 14 10:55:54.666: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:54.666: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:54.666: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:54.666: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:54.666: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:54.666: INFO:
Nov 14 10:55:56.672: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:56.672: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:56.672: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:56.672: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
Nov 14 10:55:56.672: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:56.672: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:56.672: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:56.672: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:56.672: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:56.672: INFO:
Nov 14 10:55:58.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:58.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:58.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:55:58.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
Nov 14 10:55:58.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:55:58.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:55:58.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:58.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:58.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:55:58.669: INFO:
Nov 14 10:56:00.668: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:00.668: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:00.668: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:00.668: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
Nov 14 10:56:00.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:56:00.668: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:56:00.668: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:00.668: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:00.668: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:00.668: INFO:
Nov 14 10:56:02.671: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:02.671: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:02.671: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:02.671: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
Nov 14 10:56:02.671: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:56:02.671: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:56:02.671: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:02.671: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:02.671: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:02.671: INFO:
Nov 14 10:56:04.675: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:04.675: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:04.675: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:04.675: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
Nov 14 10:56:04.675: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:56:04.675: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:56:04.675: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:04.675: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:04.675: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:04.675: INFO:
Nov 14 10:56:06.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:06.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:06.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:06.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Nov 14 10:56:06.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:56:06.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:56:06.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:06.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:06.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:06.667: INFO:
Nov 14 10:56:08.667: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:08.667: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:08.667: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:08.667: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Nov 14 10:56:08.667: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:56:08.667: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:56:08.667: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:08.667: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:08.667: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:08.667: INFO:
Nov 14 10:56:10.669: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:10.669: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:10.669: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:10.669: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 14 10:56:10.669: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:56:10.669: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:56:10.669: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:10.669: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:10.669: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:10.669: INFO:
Nov 14 10:56:10.799: INFO: The status of Pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:10.799: INFO: The status of Pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:10.799: INFO: The status of Pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 10:56:10.799: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 14 10:56:10.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 10:56:10.799: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:56:10.799: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:10.799: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:10.799: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:10.799: INFO:
�[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m11/14/22 10:56:10.799�[0m
�[1mSTEP:�[0m Found 126 events. �[38;5;243m11/14/22 10:56:10.853�[0m
Nov 14 10:56:10.853: INFO: At 2022-11-14 10:41:18 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-na43zb-control-plane-f5n7l_f772daba-d472-40f8-bea6-8567dbb601b8 became leader
Nov 14 10:56:10.853: INFO: At 2022-11-14 10:41:18 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-na43zb-control-plane-f5n7l_f01b4c9a-efe5-4bb6-a477-ed4e6893a0db became leader
Nov 14 10:56:10.853: INFO: At 2022-11-14 10:41:25 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-787d4945fb to 2
Nov 14 10:56:10.853: INFO: At 2022-11-14 10:41:25 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-qjghx
Nov 14 10:56:10.853: INFO: At 2022-11-14 10:41:25 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-jbdpg
Nov 14 10:56:10.853: INFO: At 2022-11-14 10:41:25 +0000 UTC - event for coredns-787d4945fb-jbdpg: {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 14 10:56:10.853: INFO: At 2022-11-14 10:41:25 +0000 UTC - event for coredns-787d4945fb-qjghx: {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 14 10:56:10.853: INFO: At 2022-11-14 10:41:25 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-ctgdp
Nov 14 10:56:10.853: INFO: At 2022-11-14 10:41:25 +0000 UTC - event for kube-proxy-ctgdp: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-ctgdp to capz-conf-na43zb-control-plane-f5n7l
Nov 14 10:56:10.853: INFO: At 2022-11-14 10:41:26 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulDelete: Deleted pod: kube-proxy-ctgdp
Nov 14 10:56:10.853: INFO: At 2022-11-14 10:41:30 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-2zqk2
Nov 14 10:56:10.853: INFO: At 2022-11-14 10:41:30 +0000 UTC - event for kube-proxy-2zqk2: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-2zqk2 to capz-conf-na43zb-control-plane-f5n7l
Nov 14 10:56:10.853: INFO: At 2022-11-14 10:41:31 +0000 UTC - event for kube-proxy-2zqk2: {kubelet capz-conf-na43zb-control-plane-f5n7l} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.76_827d1e9175babd"
Nov 14 10:56:10.853: INFO: At 2022-11-14 10:41:34 +0000 UTC - event for kube-proxy-2zqk2: {kubelet capz-conf-na43zb-control-plane-f5n7l} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.76_827d1e9175babd" in 2.391004882s (2.391011383s including waiting)
Nov 14 10:56:10.853: INFO: At 2022-11-14 10:41:34 +0000 UTC - event for kube-proxy-2zqk2: {kubelet capz-conf-na43zb-control-plane-f5n7l} Created: Created container kube-proxy
Nov 14 10:56:10.853: INFO: At 2022-11-14 10:41:34 +0000 UTC - event for kube-proxy-2zqk2: {kubelet capz-conf-na43zb-control-plane-f5n7l} Started: Started container kube-proxy
Nov 14 10:56:10.853: INFO: At 2022-11-14 10:41:39 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:39 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-w84pk
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:39 +0000 UTC - event for metrics-server-c9574f845-w84pk: {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 14 10:56:10.854: INFO: At 2022-11-14 10:41:40 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:40 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-x26nd
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:40 +0000 UTC - event for calico-kube-controllers-657b584867-x26nd: {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 14 10:56:10.854: INFO: At 2022-11-14 10:41:40 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-zqsw4
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:40 +0000 UTC - event for calico-node-zqsw4: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-zqsw4 to capz-conf-na43zb-control-plane-f5n7l
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:41 +0000 UTC - event for calico-node-zqsw4: {kubelet capz-conf-na43zb-control-plane-f5n7l} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:47 +0000 UTC - event for calico-node-zqsw4: {kubelet capz-conf-na43zb-control-plane-f5n7l} Created: Created container upgrade-ipam
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:47 +0000 UTC - event for calico-node-zqsw4: {kubelet capz-conf-na43zb-control-plane-f5n7l} Started: Started container upgrade-ipam
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:47 +0000 UTC - event for calico-node-zqsw4: {kubelet capz-conf-na43zb-control-plane-f5n7l} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 6.468758684s (6.468763184s including waiting)
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:51 +0000 UTC - event for calico-node-zqsw4: {kubelet capz-conf-na43zb-control-plane-f5n7l} Started: Started container install-cni
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:51 +0000 UTC - event for calico-node-zqsw4: {kubelet capz-conf-na43zb-control-plane-f5n7l} Created: Created container install-cni
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:51 +0000 UTC - event for calico-node-zqsw4: {kubelet capz-conf-na43zb-control-plane-f5n7l} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:53 +0000 UTC - event for calico-kube-controllers-657b584867-x26nd: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-x26nd to capz-conf-na43zb-control-plane-f5n7l
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:53 +0000 UTC - event for coredns-787d4945fb-jbdpg: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-jbdpg to capz-conf-na43zb-control-plane-f5n7l
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:53 +0000 UTC - event for coredns-787d4945fb-qjghx: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-qjghx to capz-conf-na43zb-control-plane-f5n7l
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:53 +0000 UTC - event for metrics-server-c9574f845-w84pk: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-w84pk to capz-conf-na43zb-control-plane-f5n7l
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:54 +0000 UTC - event for calico-kube-controllers-657b584867-x26nd: {kubelet capz-conf-na43zb-control-plane-f5n7l} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "e66b1e8cb0b1da98d9bbea0f47358fac1765b940b0eaa5102a331c18422df348": 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 14 10:56:10.854: INFO: At 2022-11-14 10:41:54 +0000 UTC - event for calico-node-zqsw4: {kubelet capz-conf-na43zb-control-plane-f5n7l} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:41:54 +0000 UTC - event for coredns-787d4945fb-jbdpg: {kubelet capz-conf-na43zb-control-plane-f5n7l} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "074027d2fc36db59e7ea200fc46fe85bd6f5e16a622918a0b61b975289541090": 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 14 10:56:10.854: INFO: At 2022-11-14 10:41:54 +0000 UTC - event for coredns-787d4945fb-qjghx: {kubelet capz-conf-na43zb-control-plane-f5n7l} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "17b853d811ed77d523762d00735f2a52f4d10cf2496280e28064ec447504ae96": 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 14 10:56:10.854: INFO: At 2022-11-14 10:41:54 +0000 UTC - event for metrics-server-c9574f845-w84pk: {kubelet capz-conf-na43zb-control-plane-f5n7l} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "35c6307e93a3d850c88c5859ef7a6b215a2c8cc7304df44c6cbc33fd7bad54da": 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 14 10:56:10.854: INFO: At 2022-11-14 10:42:00 +0000 UTC - event for calico-node-zqsw4: {kubelet capz-conf-na43zb-control-plane-f5n7l} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 6.325230358s (6.325235958s including waiting)
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:00 +0000 UTC - event for calico-node-zqsw4: {kubelet capz-conf-na43zb-control-plane-f5n7l} Created: Created container calico-node
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:00 +0000 UTC - event for calico-node-zqsw4: {kubelet capz-conf-na43zb-control-plane-f5n7l} Started: Started container calico-node
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:01 +0000 UTC - event for calico-node-zqsw4: {kubelet capz-conf-na43zb-control-plane-f5n7l} 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 14 10:56:10.854: INFO: At 2022-11-14 10:42:05 +0000 UTC - event for coredns-787d4945fb-qjghx: {kubelet capz-conf-na43zb-control-plane-f5n7l} Created: Created container coredns
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:05 +0000 UTC - event for coredns-787d4945fb-qjghx: {kubelet capz-conf-na43zb-control-plane-f5n7l} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:05 +0000 UTC - event for coredns-787d4945fb-qjghx: {kubelet capz-conf-na43zb-control-plane-f5n7l} Started: Started container coredns
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:05 +0000 UTC - event for metrics-server-c9574f845-w84pk: {kubelet capz-conf-na43zb-control-plane-f5n7l} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:06 +0000 UTC - event for coredns-787d4945fb-qjghx: {kubelet capz-conf-na43zb-control-plane-f5n7l} Unhealthy: Readiness probe failed: Get "http://192.168.185.65:8181/ready": dial tcp 192.168.185.65:8181: connect: connection refused
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:07 +0000 UTC - event for coredns-787d4945fb-jbdpg: {kubelet capz-conf-na43zb-control-plane-f5n7l} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:07 +0000 UTC - event for coredns-787d4945fb-jbdpg: {kubelet capz-conf-na43zb-control-plane-f5n7l} Created: Created container coredns
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:07 +0000 UTC - event for coredns-787d4945fb-jbdpg: {kubelet capz-conf-na43zb-control-plane-f5n7l} Started: Started container coredns
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:08 +0000 UTC - event for calico-kube-controllers-657b584867-x26nd: {kubelet capz-conf-na43zb-control-plane-f5n7l} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0"
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:08 +0000 UTC - event for coredns-787d4945fb-jbdpg: {kubelet capz-conf-na43zb-control-plane-f5n7l} Unhealthy: Readiness probe failed: Get "http://192.168.185.67:8181/ready": dial tcp 192.168.185.67:8181: connect: connection refused
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:10 +0000 UTC - event for metrics-server-c9574f845-w84pk: {kubelet capz-conf-na43zb-control-plane-f5n7l} Started: Started container metrics-server
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:10 +0000 UTC - event for metrics-server-c9574f845-w84pk: {kubelet capz-conf-na43zb-control-plane-f5n7l} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 4.573033233s (4.573106829s including waiting)
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:10 +0000 UTC - event for metrics-server-c9574f845-w84pk: {kubelet capz-conf-na43zb-control-plane-f5n7l} Created: Created container metrics-server
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:15 +0000 UTC - event for calico-kube-controllers-657b584867-x26nd: {kubelet capz-conf-na43zb-control-plane-f5n7l} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 5.036732513s (6.485343002s including waiting)
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:15 +0000 UTC - event for calico-kube-controllers-657b584867-x26nd: {kubelet capz-conf-na43zb-control-plane-f5n7l} Created: Created container calico-kube-controllers
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:42:15 +0000 UTC - event for calico-kube-controllers-657b584867-x26nd: {kubelet capz-conf-na43zb-control-plane-f5n7l} Started: Started container calico-kube-controllers
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:07 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-jxggh
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:07 +0000 UTC - event for calico-node-windows-jxggh: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-jxggh to capz-conf-zdwnq
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:07 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-xw9gb
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:07 +0000 UTC - event for containerd-logger-xw9gb: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-xw9gb to capz-conf-zdwnq
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:07 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-5vtxx
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:07 +0000 UTC - event for kube-proxy-windows-5vtxx: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-5vtxx to capz-conf-zdwnq
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:10 +0000 UTC - event for kube-proxy-windows-5vtxx: {kubelet capz-conf-zdwnq} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:26 +0000 UTC - event for calico-node-windows-jxggh: {kubelet capz-conf-zdwnq} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:26 +0000 UTC - event for containerd-logger-xw9gb: {kubelet capz-conf-zdwnq} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:26 +0000 UTC - event for kube-proxy-windows-5vtxx: {kubelet capz-conf-zdwnq} Started: Started container kube-proxy
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:26 +0000 UTC - event for kube-proxy-windows-5vtxx: {kubelet capz-conf-zdwnq} Pulled: Container image "sigwindowstools/kube-proxy:v1.26.0-beta.0.65_8e48df13531802-calico-hostprocess" already present on machine
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:26 +0000 UTC - event for kube-proxy-windows-5vtxx: {kubelet capz-conf-zdwnq} Created: Created container kube-proxy
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:29 +0000 UTC - event for calico-node-windows-jxggh: {kubelet capz-conf-zdwnq} Created: Created container install-cni
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:29 +0000 UTC - event for calico-node-windows-jxggh: {kubelet capz-conf-zdwnq} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 3.8446435s (3.8446435s including waiting)
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:30 +0000 UTC - event for calico-node-windows-jxggh: {kubelet capz-conf-zdwnq} Started: Started container install-cni
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:31 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-lm94x
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:31 +0000 UTC - event for csi-proxy-lm94x: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-lm94x to capz-conf-zdwnq
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:32 +0000 UTC - event for csi-proxy-lm94x: {kubelet capz-conf-zdwnq} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:34 +0000 UTC - event for containerd-logger-xw9gb: {kubelet capz-conf-zdwnq} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 4.2801926s (8.066325s including waiting)
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:35 +0000 UTC - event for calico-node-windows-jxggh: {kubelet capz-conf-zdwnq} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:39 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-hstrc
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:39 +0000 UTC - event for calico-node-windows-hstrc: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-hstrc to capz-conf-9z748
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:39 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-9m7lf
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:39 +0000 UTC - event for containerd-logger-9m7lf: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-9m7lf to capz-conf-9z748
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:39 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-fchls
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:39 +0000 UTC - event for kube-proxy-windows-fchls: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-fchls to capz-conf-9z748
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:41 +0000 UTC - event for kube-proxy-windows-fchls: {kubelet capz-conf-9z748} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:42 +0000 UTC - event for containerd-logger-xw9gb: {kubelet capz-conf-zdwnq} Created: Created container containerd-logger
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:42 +0000 UTC - event for containerd-logger-xw9gb: {kubelet capz-conf-zdwnq} Started: Started container containerd-logger
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:51 +0000 UTC - event for csi-proxy-lm94x: {kubelet capz-conf-zdwnq} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 16.9621672s (18.6698516s including waiting)
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:51 +0000 UTC - event for csi-proxy-lm94x: {kubelet capz-conf-zdwnq} Created: Created container csi-proxy
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:51 +0000 UTC - event for csi-proxy-lm94x: {kubelet capz-conf-zdwnq} Started: Started container csi-proxy
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:54 +0000 UTC - event for calico-node-windows-jxggh: {kubelet capz-conf-zdwnq} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:54 +0000 UTC - event for calico-node-windows-jxggh: {kubelet capz-conf-zdwnq} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 3.08158s (19.2007406s including waiting)
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:54 +0000 UTC - event for calico-node-windows-jxggh: {kubelet capz-conf-zdwnq} Created: Created container calico-node-startup
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:54 +0000 UTC - event for calico-node-windows-jxggh: {kubelet capz-conf-zdwnq} Started: Started container calico-node-startup
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:44:54 +0000 UTC - event for calico-node-windows-jxggh: {kubelet capz-conf-zdwnq} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 364.0099ms (364.0099ms including waiting)
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:00 +0000 UTC - event for calico-node-windows-jxggh: {kubelet capz-conf-zdwnq} Started: Started container calico-node-felix
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:00 +0000 UTC - event for calico-node-windows-jxggh: {kubelet capz-conf-zdwnq} Created: Created container calico-node-felix
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:00 +0000 UTC - event for containerd-logger-9m7lf: {kubelet capz-conf-9z748} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:00 +0000 UTC - event for kube-proxy-windows-fchls: {kubelet capz-conf-9z748} Pulled: Container image "sigwindowstools/kube-proxy:v1.26.0-beta.0.65_8e48df13531802-calico-hostprocess" already present on machine
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:01 +0000 UTC - event for calico-node-windows-hstrc: {kubelet capz-conf-9z748} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:01 +0000 UTC - event for kube-proxy-windows-fchls: {kubelet capz-conf-9z748} Created: Created container kube-proxy
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:01 +0000 UTC - event for kube-proxy-windows-fchls: {kubelet capz-conf-9z748} Started: Started container kube-proxy
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:05 +0000 UTC - event for containerd-logger-9m7lf: {kubelet capz-conf-9z748} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 4.6283908s (4.6283908s including waiting)
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:11 +0000 UTC - event for calico-node-windows-hstrc: {kubelet capz-conf-9z748} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 6.2842796s (10.8378115s including waiting)
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:12 +0000 UTC - event for calico-node-windows-hstrc: {kubelet capz-conf-9z748} Started: Started container install-cni
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:12 +0000 UTC - event for calico-node-windows-hstrc: {kubelet capz-conf-9z748} Created: Created container install-cni
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:14 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-dvj7f
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:14 +0000 UTC - event for csi-proxy-dvj7f: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-dvj7f to capz-conf-9z748
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:14 +0000 UTC - event for csi-proxy-dvj7f: {kubelet capz-conf-9z748} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:16 +0000 UTC - event for containerd-logger-9m7lf: {kubelet capz-conf-9z748} Started: Started container containerd-logger
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:16 +0000 UTC - event for containerd-logger-9m7lf: {kubelet capz-conf-9z748} Created: Created container containerd-logger
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:17 +0000 UTC - event for calico-node-windows-hstrc: {kubelet capz-conf-9z748} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:22 +0000 UTC - event for calico-node-windows-jxggh: {kubelet capz-conf-zdwnq} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 393.0745ms (393.0745ms including waiting)
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:33 +0000 UTC - event for csi-proxy-dvj7f: {kubelet capz-conf-9z748} Created: Created container csi-proxy
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:33 +0000 UTC - event for csi-proxy-dvj7f: {kubelet capz-conf-9z748} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 18.2137821s (18.2137821s including waiting)
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:33 +0000 UTC - event for csi-proxy-dvj7f: {kubelet capz-conf-9z748} Started: Started container csi-proxy
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:36 +0000 UTC - event for calico-node-windows-hstrc: {kubelet capz-conf-9z748} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 3.6735714s (18.880818s including waiting)
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:36 +0000 UTC - event for calico-node-windows-hstrc: {kubelet capz-conf-9z748} Created: Created container calico-node-startup
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:37 +0000 UTC - event for calico-node-windows-hstrc: {kubelet capz-conf-9z748} Started: Started container calico-node-startup
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:37 +0000 UTC - event for calico-node-windows-hstrc: {kubelet capz-conf-9z748} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:37 +0000 UTC - event for calico-node-windows-hstrc: {kubelet capz-conf-9z748} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 419.6964ms (419.6964ms including waiting)
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:44 +0000 UTC - event for calico-node-windows-hstrc: {kubelet capz-conf-9z748} Created: Created container calico-node-felix
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:45:44 +0000 UTC - event for calico-node-windows-hstrc: {kubelet capz-conf-9z748} Started: Started container calico-node-felix
Nov 14 10:56:10.854: INFO: At 2022-11-14 10:46:07 +0000 UTC - event for calico-node-windows-hstrc: {kubelet capz-conf-9z748} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 424.7926ms (424.7926ms including waiting)
Nov 14 10:56:10.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 10:56:10.911: INFO: calico-kube-controllers-657b584867-x26nd capz-conf-na43zb-control-plane-f5n7l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:53 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:16 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:16 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:53 +0000 UTC }]
Nov 14 10:56:10.911: INFO: calico-node-windows-hstrc capz-conf-9z748 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:17 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:16 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:46:16 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:39 +0000 UTC }]
Nov 14 10:56:10.911: INFO: calico-node-windows-jxggh capz-conf-zdwnq Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:35 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:29 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:29 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:07 +0000 UTC }]
Nov 14 10:56:10.911: INFO: calico-node-zqsw4 capz-conf-na43zb-control-plane-f5n7l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:54 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:02 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:02 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:40 +0000 UTC }]
Nov 14 10:56:10.911: INFO: containerd-logger-9m7lf capz-conf-9z748 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:40 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:16 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:16 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:39 +0000 UTC }]
Nov 14 10:56:10.911: INFO: containerd-logger-xw9gb capz-conf-zdwnq Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:08 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:43 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:43 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:07 +0000 UTC }]
Nov 14 10:56:10.911: INFO: coredns-787d4945fb-jbdpg capz-conf-na43zb-control-plane-f5n7l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:53 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:13 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:13 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:53 +0000 UTC }]
Nov 14 10:56:10.911: INFO: coredns-787d4945fb-qjghx capz-conf-na43zb-control-plane-f5n7l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:53 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:13 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:13 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:53 +0000 UTC }]
Nov 14 10:56:10.911: INFO: csi-proxy-dvj7f capz-conf-9z748 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:14 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:34 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:34 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:14 +0000 UTC }]
Nov 14 10:56:10.911: INFO: csi-proxy-lm94x capz-conf-zdwnq Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:31 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:52 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:52 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:31 +0000 UTC }]
Nov 14 10:56:10.911: INFO: etcd-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:27 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:32 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:32 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:27 +0000 UTC }]
Nov 14 10:56:10.911: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:10.911: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:10.911: INFO: kube-proxy-2zqk2 capz-conf-na43zb-control-plane-f5n7l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:30 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:35 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:35 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:30 +0000 UTC }]
Nov 14 10:56:10.911: INFO: kube-proxy-windows-5vtxx capz-conf-zdwnq Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:08 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:26 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:26 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:07 +0000 UTC }]
Nov 14 10:56:10.911: INFO: kube-proxy-windows-fchls capz-conf-9z748 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:40 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:01 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:45:01 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:44:39 +0000 UTC }]
Nov 14 10:56:10.911: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Nov 14 10:56:10.911: INFO: metrics-server-c9574f845-w84pk capz-conf-na43zb-control-plane-f5n7l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:53 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:34 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:42:34 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 10:41:53 +0000 UTC }]
Nov 14 10:56:10.911: INFO:
Nov 14 10:56:11.386: INFO:
Logging node info for node capz-conf-9z748
Nov 14 10:56:11.576: INFO: Node Info: &Node{ObjectMeta:{capz-conf-9z748 3d1bec6c-3e9e-47aa-a9bd-323dbc2dd8d5 2069 0 2022-11-14 10:44:39 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D4s_v3 beta.kubernetes.io/os:windows failure-domain.beta.kubernetes.io/region:canadacentral failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-9z748 kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-na43zb cluster.x-k8s.io/cluster-namespace:capz-conf-na43zb cluster.x-k8s.io/machine:capz-conf-na43zb-md-win-6dd8df958-pbq77 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-na43zb-md-win-6dd8df958 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.145.129 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:d3:c9:18 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-14 10:44:39 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-14 10:44:39 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:node.kubernetes.io/windows-build":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2022-11-14 10:45:14 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-14 10:45:58 +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-14 10:46:04 +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-14 10:55:52 +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-na43zb/providers/Microsoft.Compute/virtualMachines/capz-conf-9z748,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-14 10:55:52 +0000 UTC,LastTransitionTime:2022-11-14 10:44:39 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-14 10:55:52 +0000 UTC,LastTransitionTime:2022-11-14 10:44:39 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-14 10:55:52 +0000 UTC,LastTransitionTime:2022-11-14 10:44:39 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-14 10:55:52 +0000 UTC,LastTransitionTime:2022-11-14 10:45:14 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-9z748,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-9z748,SystemUUID:19A4EA1B-E6AA-4A1A-97F0-A9DB1DF9D899,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.26.0-beta.0.76+827d1e9175babd-dirty,KubeProxyVersion:v1.26.0-beta.0.76+827d1e9175babd-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.26.0-beta.0.65_8e48df13531802-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 14 10:56:11.577: INFO:
Logging kubelet events for node capz-conf-9z748
Nov 14 10:56:11.773: INFO:
Logging pods the kubelet thinks is on node capz-conf-9z748
Nov 14 10:56:11.992: INFO: kube-proxy-windows-fchls started at 2022-11-14 10:44:40 +0000 UTC (0+1 container statuses recorded)
Nov 14 10:56:11.992: INFO: Container kube-proxy ready: true, restart count 0
Nov 14 10:56:11.992: INFO: calico-node-windows-hstrc started at 2022-11-14 10:44:40 +0000 UTC (1+2 container statuses recorded)
Nov 14 10:56:11.992: INFO: Init container install-cni ready: true, restart count 0
Nov 14 10:56:11.992: INFO: Container calico-node-felix ready: true, restart count 1
Nov 14 10:56:11.992: INFO: Container calico-node-startup ready: true, restart count 0
Nov 14 10:56:11.992: INFO: containerd-logger-9m7lf started at 2022-11-14 10:44:40 +0000 UTC (0+1 container statuses recorded)
Nov 14 10:56:11.992: INFO: Container containerd-logger ready: true, restart count 0
Nov 14 10:56:11.992: INFO: csi-proxy-dvj7f started at 2022-11-14 10:45:14 +0000 UTC (0+1 container statuses recorded)
Nov 14 10:56:11.992: INFO: Container csi-proxy ready: true, restart count 0
Nov 14 10:56:12.644: INFO:
Latency metrics for node capz-conf-9z748
Nov 14 10:56:12.644: INFO:
Logging node info for node capz-conf-na43zb-control-plane-f5n7l
Nov 14 10:56:12.776: INFO: Node Info: &Node{ObjectMeta:{capz-conf-na43zb-control-plane-f5n7l f97dc27b-3f9d-4a85-a5a6-e2a5ee42d89a 1780 0 2022-11-14 10:41:24 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:canadacentral failure-domain.beta.kubernetes.io/zone:canadacentral-3 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-na43zb-control-plane-f5n7l kubernetes.io/os:linux node-role.kubernetes.io/control-plane: node.kubernetes.io/exclude-from-external-load-balancers: node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:canadacentral-3] map[cluster.x-k8s.io/cluster-name:capz-conf-na43zb cluster.x-k8s.io/cluster-namespace:capz-conf-na43zb cluster.x-k8s.io/machine:capz-conf-na43zb-control-plane-6lxrl cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-na43zb-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.185.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2022-11-14 10:41:24 +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-14 10:41:25 +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-14 10:41:37 +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-14 10:41:53 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2022-11-14 10:42:00 +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-14 10:52:38 +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-na43zb/providers/Microsoft.Compute/virtualMachines/capz-conf-na43zb-control-plane-f5n7l,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-14 10:42:00 +0000 UTC,LastTransitionTime:2022-11-14 10:42:00 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-14 10:52:38 +0000 UTC,LastTransitionTime:2022-11-14 10:41:00 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-14 10:52:38 +0000 UTC,LastTransitionTime:2022-11-14 10:41:00 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-14 10:52:38 +0000 UTC,LastTransitionTime:2022-11-14 10:41:00 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-14 10:52:38 +0000 UTC,LastTransitionTime:2022-11-14 10:41:53 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-na43zb-control-plane-f5n7l,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:9f40179e282c4f0385a5da2292beb1a8,SystemUUID:ed4f718d-9e6f-0d47-b7d4-cd0b8d3d31bf,BootID:be693903-30b8-4f1b-8c23-10697f3b8f73,KernelVersion:5.4.0-1091-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.26.0-beta.0.76+827d1e9175babd,KubeProxyVersion:v1.26.0-beta.0.76+827d1e9175babd,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:ec69d1434d36d220ed8080dce242380284d4166daacb073dbc6d82e11bb1d9c4 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.26.0-beta.0.65_8e48df13531802],SizeBytes:35316538,},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:bca35bdba72c14884db646f3bbf5334247c840b47a196ba6aad1bd4a8481bef0 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.26.0-beta.0.65_8e48df13531802],SizeBytes:32240596,},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:fbd439680dd72c3e4facc929a7a135d11fbf949e2099357d50b28132d086ccd9 gcr.io/k8s-staging-ci-images/kube-proxy:v1.26.0-beta.0.65_8e48df13531802],SizeBytes:21534778,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:8ec34c26f04fd61a6c4ba7c0b678c8e62942d9d9d6371c6f2042e0471df065ea capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.76_827d1e9175babd],SizeBytes:21532924,},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:ba0a3921d93c8461119feb344fd9341c2e128206857da6ad515d5da42378e9b1 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.26.0-beta.0.65_8e48df13531802],SizeBytes:17482660,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:f478aa916568b00269068ff1e9ff742ecc16192eb6e371e30f69f75df904162e registry.k8s.io/kube-scheduler:v1.25.3],SizeBytes:15798744,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Nov 14 10:56:12.777: INFO:
Logging kubelet events for node capz-conf-na43zb-control-plane-f5n7l
Nov 14 10:56:12.973: INFO:
Logging pods the kubelet thinks is on node capz-conf-na43zb-control-plane-f5n7l
Nov 14 10:56:13.211: INFO: kube-scheduler-capz-conf-na43zb-control-plane-f5n7l started at <nil> (0+0 container statuses recorded)
Nov 14 10:56:13.211: INFO: calico-node-zqsw4 started at 2022-11-14 10:41:40 +0000 UTC (2+1 container statuses recorded)
Nov 14 10:56:13.211: INFO: Init container upgrade-ipam ready: true, restart count 0
Nov 14 10:56:13.211: INFO: Init container install-cni ready: true, restart count 0
Nov 14 10:56:13.211: INFO: Container calico-node ready: true, restart count 0
Nov 14 10:56:13.211: INFO: calico-kube-controllers-657b584867-x26nd started at 2022-11-14 10:41:53 +0000 UTC (0+1 container statuses recorded)
Nov 14 10:56:13.211: INFO: Container calico-kube-controllers ready: true, restart count 0
Nov 14 10:56:13.211: INFO: coredns-787d4945fb-qjghx started at 2022-11-14 10:41:53 +0000 UTC (0+1 container statuses recorded)
Nov 14 10:56:13.211: INFO: Container coredns ready: true, restart count 0
Nov 14 10:56:13.211: INFO: kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l started at <nil> (0+0 container statuses recorded)
Nov 14 10:56:13.212: INFO: etcd-capz-conf-na43zb-control-plane-f5n7l started at 2022-11-14 10:41:27 +0000 UTC (0+1 container statuses recorded)
Nov 14 10:56:13.212: INFO: Container etcd ready: true, restart count 0
Nov 14 10:56:13.212: INFO: kube-apiserver-capz-conf-na43zb-control-plane-f5n7l started at <nil> (0+0 container statuses recorded)
Nov 14 10:56:13.212: INFO: kube-proxy-2zqk2 started at 2022-11-14 10:41:30 +0000 UTC (0+1 container statuses recorded)
Nov 14 10:56:13.212: INFO: Container kube-proxy ready: true, restart count 0
Nov 14 10:56:13.212: INFO: coredns-787d4945fb-jbdpg started at 2022-11-14 10:41:53 +0000 UTC (0+1 container statuses recorded)
Nov 14 10:56:13.212: INFO: Container coredns ready: true, restart count 0
Nov 14 10:56:13.212: INFO: metrics-server-c9574f845-w84pk started at 2022-11-14 10:41:53 +0000 UTC (0+1 container statuses recorded)
Nov 14 10:56:13.212: INFO: Container metrics-server ready: true, restart count 0
Nov 14 10:56:13.827: INFO:
Latency metrics for node capz-conf-na43zb-control-plane-f5n7l
Nov 14 10:56:13.827: INFO:
Logging node info for node capz-conf-zdwnq
Nov 14 10:56:13.974: INFO: Node Info: &Node{ObjectMeta:{capz-conf-zdwnq 5823964b-530c-41c4-8591-2cf9f8767b0b 2019 0 2022-11-14 10:44:07 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D4s_v3 beta.kubernetes.io/os:windows failure-domain.beta.kubernetes.io/region:canadacentral failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-zdwnq kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-na43zb cluster.x-k8s.io/cluster-namespace:capz-conf-na43zb cluster.x-k8s.io/machine:capz-conf-na43zb-md-win-6dd8df958-pd66b cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-na43zb-md-win-6dd8df958 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.40.1 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:1b:e6:6a volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet.exe Update v1 2022-11-14 10:44:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:node.kubernetes.io/windows-build":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kubeadm Update v1 2022-11-14 10:44:08 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kube-controller-manager Update v1 2022-11-14 10:44:31 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-14 10:44:55 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {Go-http-client Update v1 2022-11-14 10:45: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-14 10:55:19 +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-na43zb/providers/Microsoft.Compute/virtualMachines/capz-conf-zdwnq,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-14 10:55:19 +0000 UTC,LastTransitionTime:2022-11-14 10:44:07 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-14 10:55:19 +0000 UTC,LastTransitionTime:2022-11-14 10:44:07 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-14 10:55:19 +0000 UTC,LastTransitionTime:2022-11-14 10:44:07 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-14 10:55:19 +0000 UTC,LastTransitionTime:2022-11-14 10:44:31 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-zdwnq,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-zdwnq,SystemUUID:392111CF-CFF9-4FD1-A6BF-D710F86CE7C1,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.26.0-beta.0.76+827d1e9175babd-dirty,KubeProxyVersion:v1.26.0-beta.0.76+827d1e9175babd-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.26.0-beta.0.65_8e48df13531802-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 14 10:56:13.974: INFO:
Logging kubelet events for node capz-conf-zdwnq
Nov 14 10:56:14.173: INFO:
Logging pods the kubelet thinks is on node capz-conf-zdwnq
Nov 14 10:56:14.382: INFO: containerd-logger-xw9gb started at 2022-11-14 10:44:08 +0000 UTC (0+1 container statuses recorded)
Nov 14 10:56:14.382: INFO: Container containerd-logger ready: true, restart count 0
Nov 14 10:56:14.382: INFO: calico-node-windows-jxggh started at 2022-11-14 10:44:08 +0000 UTC (1+2 container statuses recorded)
Nov 14 10:56:14.382: INFO: Init container install-cni ready: true, restart count 0
Nov 14 10:56:14.382: INFO: Container calico-node-felix ready: true, restart count 1
Nov 14 10:56:14.382: INFO: Container calico-node-startup ready: true, restart count 0
Nov 14 10:56:14.382: INFO: kube-proxy-windows-5vtxx started at 2022-11-14 10:44:08 +0000 UTC (0+1 container statuses recorded)
Nov 14 10:56:14.382: INFO: Container kube-proxy ready: true, restart count 0
Nov 14 10:56:14.382: INFO: csi-proxy-lm94x started at 2022-11-14 10:44:31 +0000 UTC (0+1 container statuses recorded)
Nov 14 10:56:14.382: INFO: Container csi-proxy ready: true, restart count 0
Nov 14 10:56:15.024: INFO:
Latency metrics for node capz-conf-zdwnq
Nov 14 10:56:15.187: INFO: Running kubectl logs on non-ready containers in kube-system
Nov 14 10:56:15.573: INFO: Failed to get logs of pod kube-apiserver-capz-conf-na43zb-control-plane-f5n7l, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-na43zb-control-plane-f5n7l)
Nov 14 10:56:15.573: INFO: Logs of kube-system/kube-apiserver-capz-conf-na43zb-control-plane-f5n7l:kube-apiserver on node capz-conf-na43zb-control-plane-f5n7l
Nov 14 10:56:15.573: INFO: : STARTLOG
ENDLOG for container kube-system:kube-apiserver-capz-conf-na43zb-control-plane-f5n7l:kube-apiserver
Nov 14 10:56:15.973: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l)
Nov 14 10:56:15.973: INFO: Logs of kube-system/kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l:kube-controller-manager on node capz-conf-na43zb-control-plane-f5n7l
Nov 14 10:56:15.973: INFO: : STARTLOG
ENDLOG for container kube-system:kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l:kube-controller-manager
Nov 14 10:56:16.374: INFO: Failed to get logs of pod kube-scheduler-capz-conf-na43zb-control-plane-f5n7l, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-na43zb-control-plane-f5n7l)
Nov 14 10:56:16.374: INFO: Logs of kube-system/kube-scheduler-capz-conf-na43zb-control-plane-f5n7l:kube-scheduler on node capz-conf-na43zb-control-plane-f5n7l
Nov 14 10:56:16.374: INFO: : STARTLOG
ENDLOG for container kube-system:kube-scheduler-capz-conf-na43zb-control-plane-f5n7l:kube-scheduler
Nov 14 10:56:16.374: 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-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
kube-controller-manager-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
kube-scheduler-capz-conf-na43zb-control-plane-f5n7l capz-conf-na43zb-control-plane-f5n7l Pending []
Full Stack Trace
k8s.io/kubernetes/test/e2e.setupSuite({0x7fa8885138f0, 0xc002f24040})
test/e2e/e2e.go:249 +0x5bf
k8s.io/kubernetes/test/e2e.glob..func1({0x7fa8885138f0, 0xc002f24040})
test/e2e/e2e.go:81 +0xaa
reflect.Value.call({0x6856240?, 0x78af028?, 0x0?}, {0x75d139a, 0x4}, {0xc0000b3f38, 0x1, 0x0?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x6856240?, 0x78af028?, 0x0?}, {0xc0000b3f38?, 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