PR #112923 pull-kubernetes-e2e-capz-windows-containerd #1592183228301578240
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 | 1h14m |
| Revision | 20ae39071d83cdf5fe4ed6a6e31674ab8c3943e5 |
| 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({0x7f0024e448d8, 0xc001264400})
test/e2e/e2e.go:249 +0x5bf
k8s.io/kubernetes/test/e2e.glob..func1({0x7f0024e448d8, 0xc001264400})
test/e2e/e2e.go:81 +0xaa
reflect.Value.call({0x6856240?, 0x78af028?, 0x13?}, {0x75d139a, 0x4}, {0xc000cb8f38, 0x1, 0x1?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x6856240?, 0x78af028?, 0x26c35ed?}, {0xc0000a2738?, 0x2651b67?, 0xc0000a2720?})
/usr/local/go/src/reflect/value.go:368 +0xbc
[SynchronizedBeforeSuite] TOP-LEVEL
test/e2e/e2e.go:77
Nov 14 16:44:14.447: INFO: >>> kubeConfig: /tmp/kubeconfig
Nov 14 16:44:14.449: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Nov 14 16:44:14.665: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Nov 14 16:44:14.794: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:14.794: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:14.794: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:14.794: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Nov 14 16:44:14.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:14.794: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:14.794: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:14.794: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:14.794: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:14.794: INFO:
Nov 14 16:44:16.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:16.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:16.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:16.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Nov 14 16:44:16.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:16.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:16.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:16.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:16.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:16.918: INFO:
Nov 14 16:44:18.916: INFO: The status of Pod calico-node-windows-zn2ld is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:18.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:18.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:18.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:18.916: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Nov 14 16:44:18.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:18.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:18.916: INFO: calico-node-windows-zn2ld capz-conf-gd96z Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:34 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:44:17 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:44:17 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:07 +0000 UTC }]
Nov 14 16:44:18.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:18.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:18.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:18.916: INFO:
Nov 14 16:44:20.917: INFO: The status of Pod calico-node-windows-n8r9c is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:20.917: INFO: The status of Pod calico-node-windows-zn2ld is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:20.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:20.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:20.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:20.917: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Nov 14 16:44:20.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:20.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:20.917: INFO: calico-node-windows-n8r9c capz-conf-7qbdc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:38 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:44:19 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:44:19 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:07 +0000 UTC }]
Nov 14 16:44:20.917: INFO: calico-node-windows-zn2ld capz-conf-gd96z Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:34 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:44:17 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:44:17 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:07 +0000 UTC }]
Nov 14 16:44:20.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:20.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:20.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:20.917: INFO:
Nov 14 16:44:22.919: INFO: The status of Pod calico-node-windows-n8r9c is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:22.919: INFO: The status of Pod calico-node-windows-zn2ld is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:22.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:22.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:22.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:22.919: INFO: 13 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Nov 14 16:44:22.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:22.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:22.919: INFO: calico-node-windows-n8r9c capz-conf-7qbdc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:38 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:44:19 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:44:19 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:07 +0000 UTC }]
Nov 14 16:44:22.919: INFO: calico-node-windows-zn2ld capz-conf-gd96z Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:34 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:44:17 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:44:17 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:07 +0000 UTC }]
Nov 14 16:44:22.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:22.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:22.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:22.919: INFO:
Nov 14 16:44:24.916: INFO: The status of Pod calico-node-windows-n8r9c is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:24.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:24.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:24.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:24.916: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Nov 14 16:44:24.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:24.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:24.916: INFO: calico-node-windows-n8r9c capz-conf-7qbdc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:38 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:44:19 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:44:19 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:07 +0000 UTC }]
Nov 14 16:44:24.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:24.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:24.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:24.916: INFO:
Nov 14 16:44:26.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:26.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:26.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:26.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Nov 14 16:44:26.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:26.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:26.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:26.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:26.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:26.920: INFO:
Nov 14 16:44:28.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:28.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:28.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:28.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Nov 14 16:44:28.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:28.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:28.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:28.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:28.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:28.918: INFO:
Nov 14 16:44:30.930: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:30.930: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:30.930: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:30.930: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Nov 14 16:44:30.930: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:30.930: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:30.930: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:30.930: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:30.930: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:30.930: INFO:
Nov 14 16:44:32.932: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:32.932: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:32.932: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:32.932: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Nov 14 16:44:32.932: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:32.932: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:32.932: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:32.932: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:32.932: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:32.932: INFO:
Nov 14 16:44:34.932: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:34.932: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:34.932: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:34.932: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Nov 14 16:44:34.932: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:34.932: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:34.932: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:34.932: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:34.932: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:34.932: INFO:
Nov 14 16:44:36.930: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:36.930: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:36.930: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:36.930: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Nov 14 16:44:36.931: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:36.931: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:36.931: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:36.931: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:36.931: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:36.931: INFO:
Nov 14 16:44:38.933: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:38.933: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:38.933: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:38.933: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Nov 14 16:44:38.933: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:38.933: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:38.933: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:38.933: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:38.933: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:38.933: INFO:
Nov 14 16:44:40.931: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:40.931: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:40.931: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:40.931: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Nov 14 16:44:40.931: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:40.931: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:40.931: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:40.931: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:40.931: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:40.931: INFO:
Nov 14 16:44:42.932: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:42.932: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:42.932: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:42.932: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Nov 14 16:44:42.932: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:42.932: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:42.932: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:42.932: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:42.932: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:42.932: INFO:
Nov 14 16:44:44.932: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:44.932: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:44.932: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:44.932: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
Nov 14 16:44:44.932: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:44.932: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:44.932: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:44.932: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:44.932: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:44.932: INFO:
Nov 14 16:44:46.948: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:46.948: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:46.948: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:46.948: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
Nov 14 16:44:46.948: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:46.948: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:46.948: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:46.948: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:46.948: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:46.948: INFO:
Nov 14 16:44:48.932: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:48.932: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:48.932: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:48.932: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
Nov 14 16:44:48.932: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:48.932: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:48.932: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:48.932: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:48.932: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:48.932: INFO:
Nov 14 16:44:50.932: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:50.932: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:50.932: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:50.932: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
Nov 14 16:44:50.932: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:50.932: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:50.932: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:50.932: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:50.932: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:50.932: INFO:
Nov 14 16:44:52.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:52.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:52.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:52.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
Nov 14 16:44:52.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:52.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:52.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:52.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:52.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:52.918: INFO:
Nov 14 16:44:54.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:54.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:54.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:54.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
Nov 14 16:44:54.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:54.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:54.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:54.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:54.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:54.919: INFO:
Nov 14 16:44:56.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:56.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:56.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:56.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
Nov 14 16:44:56.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:56.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:56.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:56.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:56.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:56.918: INFO:
Nov 14 16:44:58.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:58.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:58.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:44:58.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
Nov 14 16:44:58.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:44:58.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:44:58.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:58.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:58.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:44:58.917: INFO:
Nov 14 16:45:00.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:00.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:00.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:00.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
Nov 14 16:45:00.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:00.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:00.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:00.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:00.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:00.918: INFO:
Nov 14 16:45:02.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:02.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:02.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:02.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
Nov 14 16:45:02.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:02.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:02.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:02.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:02.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:02.920: INFO:
Nov 14 16:45:04.922: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:04.922: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:04.922: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:04.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
Nov 14 16:45:04.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:04.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:04.922: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:04.922: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:04.922: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:04.922: INFO:
Nov 14 16:45:06.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:06.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:06.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:06.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
Nov 14 16:45:06.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:06.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:06.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:06.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:06.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:06.918: INFO:
Nov 14 16:45:08.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:08.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:08.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:08.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
Nov 14 16:45:08.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:08.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:08.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:08.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:08.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:08.919: INFO:
Nov 14 16:45:10.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:10.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:10.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:10.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
Nov 14 16:45:10.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:10.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:10.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:10.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:10.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:10.917: INFO:
Nov 14 16:45:12.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:12.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:12.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:12.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
Nov 14 16:45:12.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:12.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:12.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:12.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:12.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:12.917: INFO:
Nov 14 16:45:14.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:14.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:14.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:14.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
Nov 14 16:45:14.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:14.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:14.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:14.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:14.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:14.920: INFO:
Nov 14 16:45:16.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:16.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:16.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:16.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
Nov 14 16:45:16.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:16.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:16.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:16.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:16.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:16.917: INFO:
Nov 14 16:45:18.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:18.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:18.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:18.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
Nov 14 16:45:18.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:18.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:18.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:18.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:18.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:18.919: INFO:
Nov 14 16:45:20.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:20.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:20.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:20.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
Nov 14 16:45:20.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:20.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:20.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:20.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:20.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:20.918: INFO:
Nov 14 16:45:22.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:22.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:22.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:22.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
Nov 14 16:45:22.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:22.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:22.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:22.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:22.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:22.917: INFO:
Nov 14 16:45:24.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:24.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:24.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:24.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
Nov 14 16:45:24.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:24.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:24.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:24.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:24.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:24.919: INFO:
Nov 14 16:45:26.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:26.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:26.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:26.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
Nov 14 16:45:26.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:26.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:26.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:26.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:26.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:26.917: INFO:
Nov 14 16:45:28.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:28.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:28.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:28.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
Nov 14 16:45:28.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:28.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:28.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:28.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:28.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:28.918: INFO:
Nov 14 16:45:30.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:30.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:30.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:30.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
Nov 14 16:45:30.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:30.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:30.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:30.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:30.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:30.917: INFO:
Nov 14 16:45:32.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:32.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:32.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:32.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
Nov 14 16:45:32.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:32.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:32.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:32.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:32.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:32.919: INFO:
Nov 14 16:45:34.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:34.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:34.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:34.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
Nov 14 16:45:34.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:34.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:34.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:34.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:34.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:34.917: INFO:
Nov 14 16:45:36.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:36.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:36.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:36.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
Nov 14 16:45:36.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:36.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:36.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:36.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:36.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:36.917: INFO:
Nov 14 16:45:38.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:38.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:38.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:38.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
Nov 14 16:45:38.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:38.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:38.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:38.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:38.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:38.916: INFO:
Nov 14 16:45:40.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:40.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:40.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:40.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
Nov 14 16:45:40.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:40.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:40.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:40.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:40.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:40.918: INFO:
Nov 14 16:45:42.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:42.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:42.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:42.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
Nov 14 16:45:42.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:42.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:42.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:42.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:42.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:42.916: INFO:
Nov 14 16:45:44.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:44.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:44.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:44.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
Nov 14 16:45:44.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:44.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:44.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:44.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:44.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:44.917: INFO:
Nov 14 16:45:46.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:46.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:46.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:46.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
Nov 14 16:45:46.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:46.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:46.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:46.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:46.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:46.917: INFO:
Nov 14 16:45:48.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:48.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:48.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:48.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
Nov 14 16:45:48.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:48.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:48.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:48.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:48.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:48.917: INFO:
Nov 14 16:45:50.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:50.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:50.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:50.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
Nov 14 16:45:50.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:50.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:50.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:50.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:50.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:50.917: INFO:
Nov 14 16:45:52.923: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:52.923: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:52.923: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:52.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
Nov 14 16:45:52.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:52.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:52.923: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:52.923: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:52.923: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:52.923: INFO:
Nov 14 16:45:54.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:54.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:54.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:54.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
Nov 14 16:45:54.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:54.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:54.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:54.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:54.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:54.916: INFO:
Nov 14 16:45:56.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:56.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:56.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:56.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
Nov 14 16:45:56.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:56.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:56.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:56.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:56.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:56.920: INFO:
Nov 14 16:45:58.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:58.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:58.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:45:58.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
Nov 14 16:45:58.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:45:58.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:45:58.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:58.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:58.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:45:58.917: INFO:
Nov 14 16:46:00.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:00.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:00.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:00.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
Nov 14 16:46:00.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:00.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:00.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:00.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:00.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:00.916: INFO:
Nov 14 16:46:02.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:02.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:02.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:02.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
Nov 14 16:46:02.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:02.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:02.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:02.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:02.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:02.916: INFO:
Nov 14 16:46:04.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:04.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:04.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:04.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
Nov 14 16:46:04.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:04.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:04.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:04.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:04.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:04.918: INFO:
Nov 14 16:46:06.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:06.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:06.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:06.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
Nov 14 16:46:06.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:06.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:06.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:06.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:06.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:06.919: INFO:
Nov 14 16:46:08.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:08.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:08.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:08.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
Nov 14 16:46:08.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:08.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:08.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:08.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:08.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:08.917: INFO:
Nov 14 16:46:10.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:10.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:10.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:10.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
Nov 14 16:46:10.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:10.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:10.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:10.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:10.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:10.917: INFO:
Nov 14 16:46:12.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:12.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:12.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:12.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
Nov 14 16:46:12.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:12.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:12.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:12.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:12.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:12.918: INFO:
Nov 14 16:46:14.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:14.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:14.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:14.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
Nov 14 16:46:14.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:14.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:14.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:14.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:14.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:14.917: INFO:
Nov 14 16:46:16.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:16.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:16.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:16.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
Nov 14 16:46:16.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:16.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:16.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:16.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:16.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:16.918: INFO:
Nov 14 16:46:18.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:18.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:18.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:18.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
Nov 14 16:46:18.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:18.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:18.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:18.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:18.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:18.919: INFO:
Nov 14 16:46:20.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:20.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:20.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:20.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
Nov 14 16:46:20.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:20.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:20.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:20.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:20.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:20.918: INFO:
Nov 14 16:46:22.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:22.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:22.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:22.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
Nov 14 16:46:22.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:22.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:22.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:22.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:22.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:22.918: INFO:
Nov 14 16:46:24.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:24.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:24.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:24.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
Nov 14 16:46:24.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:24.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:24.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:24.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:24.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:24.917: INFO:
Nov 14 16:46:26.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:26.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:26.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:26.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
Nov 14 16:46:26.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:26.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:26.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:26.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:26.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:26.917: INFO:
Nov 14 16:46:28.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:28.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:28.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:28.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
Nov 14 16:46:28.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:28.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:28.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:28.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:28.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:28.917: INFO:
Nov 14 16:46:30.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:30.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:30.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:30.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
Nov 14 16:46:30.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:30.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:30.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:30.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:30.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:30.917: INFO:
Nov 14 16:46:32.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:32.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:32.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:32.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
Nov 14 16:46:32.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:32.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:32.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:32.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:32.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:32.916: INFO:
Nov 14 16:46:34.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:34.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:34.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:34.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
Nov 14 16:46:34.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:34.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:34.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:34.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:34.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:34.916: INFO:
Nov 14 16:46:36.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:36.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:36.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:36.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
Nov 14 16:46:36.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:36.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:36.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:36.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:36.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:36.918: INFO:
Nov 14 16:46:38.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:38.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:38.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:38.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
Nov 14 16:46:38.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:38.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:38.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:38.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:38.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:38.918: INFO:
Nov 14 16:46:40.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:40.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:40.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:40.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
Nov 14 16:46:40.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:40.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:40.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:40.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:40.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:40.917: INFO:
Nov 14 16:46:42.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:42.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:42.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:42.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
Nov 14 16:46:42.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:42.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:42.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:42.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:42.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:42.918: INFO:
Nov 14 16:46:44.925: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:44.925: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:44.925: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:44.925: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
Nov 14 16:46:44.925: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:44.925: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:44.925: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:44.925: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:44.925: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:44.925: INFO:
Nov 14 16:46:46.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:46.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:46.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:46.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
Nov 14 16:46:46.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:46.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:46.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:46.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:46.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:46.917: INFO:
Nov 14 16:46:48.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:48.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:48.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:48.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
Nov 14 16:46:48.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:48.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:48.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:48.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:48.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:48.917: INFO:
Nov 14 16:46:50.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:50.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:50.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:50.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
Nov 14 16:46:50.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:50.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:50.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:50.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:50.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:50.917: INFO:
Nov 14 16:46:52.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:52.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:52.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:52.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
Nov 14 16:46:52.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:52.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:52.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:52.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:52.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:52.916: INFO:
Nov 14 16:46:54.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:54.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:54.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:54.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
Nov 14 16:46:54.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:54.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:54.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:54.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:54.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:54.917: INFO:
Nov 14 16:46:56.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:56.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:56.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:56.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
Nov 14 16:46:56.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:56.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:56.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:56.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:56.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:56.917: INFO:
Nov 14 16:46:58.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:58.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:58.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:46:58.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
Nov 14 16:46:58.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:46:58.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:46:58.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:58.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:58.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:46:58.917: INFO:
Nov 14 16:47:00.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:00.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:00.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:00.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
Nov 14 16:47:00.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:00.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:00.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:00.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:00.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:00.918: INFO:
Nov 14 16:47:02.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:02.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:02.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:02.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
Nov 14 16:47:02.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:02.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:02.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:02.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:02.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:02.917: INFO:
Nov 14 16:47:04.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:04.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:04.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:04.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
Nov 14 16:47:04.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:04.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:04.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:04.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:04.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:04.916: INFO:
Nov 14 16:47:06.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:06.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:06.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:06.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
Nov 14 16:47:06.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:06.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:06.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:06.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:06.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:06.917: INFO:
Nov 14 16:47:08.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:08.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:08.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:08.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
Nov 14 16:47:08.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:08.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:08.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:08.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:08.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:08.919: INFO:
Nov 14 16:47:10.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:10.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:10.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:10.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
Nov 14 16:47:10.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:10.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:10.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:10.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:10.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:10.916: INFO:
Nov 14 16:47:12.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:12.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:12.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:12.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
Nov 14 16:47:12.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:12.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:12.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:12.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:12.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:12.916: INFO:
Nov 14 16:47:14.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:14.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:14.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:14.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
Nov 14 16:47:14.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:14.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:14.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:14.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:14.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:14.919: INFO:
Nov 14 16:47:16.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:16.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:16.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:16.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
Nov 14 16:47:16.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:16.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:16.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:16.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:16.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:16.916: INFO:
Nov 14 16:47:18.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:18.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:18.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:18.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
Nov 14 16:47:18.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:18.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:18.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:18.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:18.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:18.917: INFO:
Nov 14 16:47:20.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:20.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:20.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:20.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
Nov 14 16:47:20.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:20.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:20.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:20.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:20.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:20.916: INFO:
Nov 14 16:47:22.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:22.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:22.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:22.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
Nov 14 16:47:22.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:22.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:22.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:22.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:22.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:22.916: INFO:
Nov 14 16:47:24.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:24.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:24.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:24.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
Nov 14 16:47:24.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:24.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:24.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:24.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:24.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:24.918: INFO:
Nov 14 16:47:26.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:26.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:26.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:26.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
Nov 14 16:47:26.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:26.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:26.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:26.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:26.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:26.917: INFO:
Nov 14 16:47:29.025: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:29.025: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:29.025: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:29.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
Nov 14 16:47:29.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:29.025: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:29.025: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:29.025: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:29.025: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:29.025: INFO:
Nov 14 16:47:30.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:30.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:30.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:30.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
Nov 14 16:47:30.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:30.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:30.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:30.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:30.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:30.917: INFO:
Nov 14 16:47:32.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:32.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:32.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:32.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
Nov 14 16:47:32.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:32.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:32.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:32.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:32.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:32.917: INFO:
Nov 14 16:47:34.926: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:34.926: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:34.926: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:34.926: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
Nov 14 16:47:34.926: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:34.926: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:34.926: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:34.926: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:34.926: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:34.926: INFO:
Nov 14 16:47:36.930: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:36.930: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:36.930: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:36.930: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
Nov 14 16:47:36.930: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:36.930: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:36.930: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:36.930: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:36.930: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:36.930: INFO:
Nov 14 16:47:38.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:38.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:38.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:38.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
Nov 14 16:47:38.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:38.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:38.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:38.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:38.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:38.916: INFO:
Nov 14 16:47:40.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:40.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:40.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:40.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
Nov 14 16:47:40.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:40.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:40.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:40.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:40.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:40.917: INFO:
Nov 14 16:47:42.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:42.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:42.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:42.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
Nov 14 16:47:42.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:42.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:42.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:42.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:42.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:42.919: INFO:
Nov 14 16:47:44.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:44.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:44.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:44.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
Nov 14 16:47:44.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:44.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:44.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:44.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:44.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:44.917: INFO:
Nov 14 16:47:46.915: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:46.915: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:46.915: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:46.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
Nov 14 16:47:46.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:46.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:46.915: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:46.915: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:46.915: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:46.915: INFO:
Nov 14 16:47:48.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:48.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:48.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:48.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
Nov 14 16:47:48.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:48.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:48.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:48.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:48.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:48.917: INFO:
Nov 14 16:47:50.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:50.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:50.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:50.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
Nov 14 16:47:50.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:50.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:50.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:50.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:50.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:50.917: INFO:
Nov 14 16:47:52.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:52.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:52.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:52.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
Nov 14 16:47:52.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:52.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:52.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:52.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:52.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:52.917: INFO:
Nov 14 16:47:54.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:54.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:54.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:54.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
Nov 14 16:47:54.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:54.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:54.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:54.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:54.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:54.917: INFO:
Nov 14 16:47:56.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:56.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:56.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:56.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
Nov 14 16:47:56.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:56.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:56.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:56.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:56.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:56.916: INFO:
Nov 14 16:47:58.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:58.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:58.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:47:58.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
Nov 14 16:47:58.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:47:58.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:47:58.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:58.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:58.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:47:58.916: INFO:
Nov 14 16:48:00.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:00.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:00.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:00.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
Nov 14 16:48:00.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:00.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:00.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:00.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:00.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:00.916: INFO:
Nov 14 16:48:02.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:02.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:02.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:02.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
Nov 14 16:48:02.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:02.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:02.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:02.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:02.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:02.917: INFO:
Nov 14 16:48:04.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:04.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:04.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:04.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
Nov 14 16:48:04.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:04.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:04.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:04.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:04.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:04.917: INFO:
Nov 14 16:48:06.915: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:06.915: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:06.915: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:06.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
Nov 14 16:48:06.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:06.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:06.915: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:06.915: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:06.915: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:06.915: INFO:
Nov 14 16:48:08.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:08.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:08.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:08.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
Nov 14 16:48:08.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:08.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:08.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:08.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:08.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:08.919: INFO:
Nov 14 16:48:10.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:10.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:10.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:10.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
Nov 14 16:48:10.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:10.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:10.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:10.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:10.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:10.916: INFO:
Nov 14 16:48:12.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:12.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:12.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:12.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
Nov 14 16:48:12.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:12.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:12.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:12.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:12.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:12.918: INFO:
Nov 14 16:48:14.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:14.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:14.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:14.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
Nov 14 16:48:14.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:14.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:14.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:14.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:14.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:14.916: INFO:
Nov 14 16:48:16.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:16.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:16.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:16.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
Nov 14 16:48:16.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:16.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:16.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:16.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:16.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:16.916: INFO:
Nov 14 16:48:18.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:18.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:18.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:18.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
Nov 14 16:48:18.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:18.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:18.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:18.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:18.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:18.917: INFO:
Nov 14 16:48:20.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:20.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:20.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:20.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
Nov 14 16:48:20.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:20.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:20.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:20.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:20.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:20.917: INFO:
Nov 14 16:48:22.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:22.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:22.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:22.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
Nov 14 16:48:22.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:22.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:22.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:22.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:22.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:22.920: INFO:
Nov 14 16:48:24.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:24.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:24.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:24.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
Nov 14 16:48:24.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:24.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:24.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:24.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:24.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:24.917: INFO:
Nov 14 16:48:26.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:26.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:26.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:26.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
Nov 14 16:48:26.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:26.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:26.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:26.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:26.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:26.920: INFO:
Nov 14 16:48:28.924: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:28.924: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:28.924: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:28.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
Nov 14 16:48:28.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:28.924: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:28.924: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:28.924: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:28.924: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:28.924: INFO:
Nov 14 16:48:30.923: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:30.923: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:30.923: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:30.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
Nov 14 16:48:30.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:30.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:30.923: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:30.923: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:30.923: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:30.923: INFO:
Nov 14 16:48:32.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:32.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:32.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:32.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
Nov 14 16:48:32.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:32.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:32.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:32.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:32.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:32.918: INFO:
Nov 14 16:48:34.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:34.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:34.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:34.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
Nov 14 16:48:34.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:34.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:34.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:34.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:34.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:34.916: INFO:
Nov 14 16:48:36.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:36.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:36.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:36.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
Nov 14 16:48:36.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:36.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:36.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:36.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:36.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:36.917: INFO:
Nov 14 16:48:38.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:38.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:38.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:38.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
Nov 14 16:48:38.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:38.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:38.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:38.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:38.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:38.919: INFO:
Nov 14 16:48:40.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:40.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:40.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:40.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
Nov 14 16:48:40.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:40.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:40.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:40.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:40.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:40.917: INFO:
Nov 14 16:48:42.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:42.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:42.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:42.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
Nov 14 16:48:42.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:42.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:42.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:42.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:42.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:42.917: INFO:
Nov 14 16:48:44.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:44.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:44.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:44.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
Nov 14 16:48:44.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:44.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:44.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:44.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:44.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:44.919: INFO:
Nov 14 16:48:46.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:46.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:46.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:46.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
Nov 14 16:48:46.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:46.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:46.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:46.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:46.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:46.916: INFO:
Nov 14 16:48:48.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:48.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:48.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:48.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
Nov 14 16:48:48.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:48.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:48.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:48.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:48.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:48.917: INFO:
Nov 14 16:48:50.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:50.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:50.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:50.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
Nov 14 16:48:50.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:50.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:50.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:50.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:50.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:50.916: INFO:
Nov 14 16:48:52.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:52.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:52.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:52.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
Nov 14 16:48:52.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:52.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:52.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:52.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:52.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:52.918: INFO:
Nov 14 16:48:54.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:54.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:54.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:54.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
Nov 14 16:48:54.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:54.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:54.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:54.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:54.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:54.921: INFO:
Nov 14 16:48:57.025: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:57.025: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:57.025: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:57.025: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
Nov 14 16:48:57.025: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:57.025: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:57.025: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:57.025: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:57.025: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:57.025: INFO:
Nov 14 16:48:58.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:58.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:58.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:48:58.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
Nov 14 16:48:58.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:48:58.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:48:58.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:58.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:58.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:48:58.920: INFO:
Nov 14 16:49:00.923: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:00.923: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:00.923: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:00.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
Nov 14 16:49:00.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:00.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:00.923: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:00.923: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:00.923: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:00.923: INFO:
Nov 14 16:49:02.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:02.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:02.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:02.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
Nov 14 16:49:02.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:02.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:02.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:02.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:02.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:02.919: INFO:
Nov 14 16:49:04.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:04.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:04.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:04.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
Nov 14 16:49:04.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:04.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:04.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:04.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:04.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:04.916: INFO:
Nov 14 16:49:06.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:06.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:06.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:06.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
Nov 14 16:49:06.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:06.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:06.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:06.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:06.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:06.917: INFO:
Nov 14 16:49:08.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:08.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:08.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:08.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
Nov 14 16:49:08.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:08.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:08.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:08.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:08.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:08.916: INFO:
Nov 14 16:49:10.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:10.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:10.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:10.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
Nov 14 16:49:10.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:10.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:10.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:10.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:10.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:10.921: INFO:
Nov 14 16:49:12.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:12.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:12.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:12.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
Nov 14 16:49:12.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:12.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:12.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:12.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:12.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:12.919: INFO:
Nov 14 16:49:14.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:14.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:14.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:14.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
Nov 14 16:49:14.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:14.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:14.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:14.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:14.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:14.918: INFO:
Nov 14 16:49:16.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:16.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:16.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:16.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
Nov 14 16:49:16.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:16.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:16.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:16.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:16.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:16.919: INFO:
Nov 14 16:49:18.924: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:18.924: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:18.924: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:18.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
Nov 14 16:49:18.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:18.924: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:18.924: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:18.924: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:18.924: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:18.924: INFO:
Nov 14 16:49:20.934: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:20.934: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:20.934: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:20.934: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
Nov 14 16:49:20.934: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:20.934: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:20.934: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:20.934: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:20.934: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:20.934: INFO:
Nov 14 16:49:22.922: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:22.922: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:22.922: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:22.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
Nov 14 16:49:22.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:22.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:22.922: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:22.923: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:22.923: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:22.923: INFO:
Nov 14 16:49:24.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:24.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:24.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:24.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
Nov 14 16:49:24.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:24.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:24.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:24.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:24.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:24.921: INFO:
Nov 14 16:49:26.923: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:26.923: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:26.923: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:26.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
Nov 14 16:49:26.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:26.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:26.923: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:26.923: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:26.923: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:26.923: INFO:
Nov 14 16:49:28.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:28.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:28.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:28.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
Nov 14 16:49:28.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:28.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:28.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:28.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:28.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:28.919: INFO:
Nov 14 16:49:30.926: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:30.926: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:30.926: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:30.926: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
Nov 14 16:49:30.926: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:30.926: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:30.926: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:30.926: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:30.926: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:30.926: INFO:
Nov 14 16:49:32.925: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:32.925: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:32.925: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:32.925: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
Nov 14 16:49:32.925: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:32.925: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:32.925: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:32.925: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:32.925: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:32.925: INFO:
Nov 14 16:49:34.924: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:34.924: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:34.924: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:34.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
Nov 14 16:49:34.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:34.924: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:34.924: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:34.924: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:34.924: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:34.924: INFO:
Nov 14 16:49:36.922: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:36.922: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:36.922: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:36.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
Nov 14 16:49:36.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:36.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:36.922: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:36.922: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:36.922: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:36.922: INFO:
Nov 14 16:49:38.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:38.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:38.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:38.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
Nov 14 16:49:38.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:38.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:38.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:38.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:38.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:38.920: INFO:
Nov 14 16:49:40.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:40.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:40.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:40.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
Nov 14 16:49:40.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:40.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:40.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:40.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:40.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:40.918: INFO:
Nov 14 16:49:42.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:42.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:42.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:42.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
Nov 14 16:49:42.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:42.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:42.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:42.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:42.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:42.920: INFO:
Nov 14 16:49:44.926: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:44.926: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:44.926: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:44.926: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
Nov 14 16:49:44.926: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:44.926: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:44.926: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:44.926: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:44.926: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:44.926: INFO:
Nov 14 16:49:46.928: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:46.928: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:46.928: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:46.928: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
Nov 14 16:49:46.928: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:46.928: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:46.928: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:46.928: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:46.928: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:46.928: INFO:
Nov 14 16:49:48.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:48.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:48.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:48.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
Nov 14 16:49:48.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:48.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:48.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:48.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:48.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:48.918: INFO:
Nov 14 16:49:50.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:50.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:50.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:50.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
Nov 14 16:49:50.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:50.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:50.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:50.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:50.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:50.919: INFO:
Nov 14 16:49:52.930: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:52.930: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:52.930: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:52.930: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
Nov 14 16:49:52.930: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:52.930: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:52.930: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:52.930: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:52.930: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:52.930: INFO:
Nov 14 16:49:54.928: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:54.929: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:54.929: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:54.929: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
Nov 14 16:49:54.929: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:54.929: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:54.929: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:54.929: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:54.929: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:54.929: INFO:
Nov 14 16:49:56.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:56.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:56.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:56.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
Nov 14 16:49:56.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:56.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:56.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:56.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:56.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:56.920: INFO:
Nov 14 16:49:58.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:58.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:58.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:49:58.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
Nov 14 16:49:58.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:49:58.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:49:58.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:58.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:58.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:49:58.920: INFO:
Nov 14 16:50:00.922: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:00.922: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:00.922: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:00.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
Nov 14 16:50:00.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:00.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:00.922: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:00.922: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:00.922: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:00.922: INFO:
Nov 14 16:50:02.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:02.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:02.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:02.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
Nov 14 16:50:02.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:02.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:02.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:02.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:02.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:02.917: INFO:
Nov 14 16:50:04.923: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:04.923: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:04.923: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:04.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
Nov 14 16:50:04.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:04.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:04.923: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:04.923: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:04.923: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:04.923: INFO:
Nov 14 16:50:06.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:06.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:06.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:06.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
Nov 14 16:50:06.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:06.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:06.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:06.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:06.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:06.916: INFO:
Nov 14 16:50:08.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:08.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:08.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:08.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
Nov 14 16:50:08.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:08.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:08.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:08.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:08.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:08.920: INFO:
Nov 14 16:50:10.936: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:10.936: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:10.936: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:10.936: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
Nov 14 16:50:10.936: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:10.936: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:10.936: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:10.936: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:10.936: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:10.936: INFO:
Nov 14 16:50:12.924: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:12.924: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:12.925: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:12.925: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
Nov 14 16:50:12.925: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:12.925: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:12.925: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:12.925: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:12.925: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:12.925: INFO:
Nov 14 16:50:14.926: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:14.926: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:14.926: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:14.926: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
Nov 14 16:50:14.926: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:14.926: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:14.926: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:14.926: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:14.926: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:14.926: INFO:
Nov 14 16:50:16.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:16.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:16.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:16.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
Nov 14 16:50:16.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:16.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:16.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:16.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:16.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:16.921: INFO:
Nov 14 16:50:18.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:18.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:18.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:18.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
Nov 14 16:50:18.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:18.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:18.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:18.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:18.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:18.919: INFO:
Nov 14 16:50:20.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:20.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:20.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:20.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
Nov 14 16:50:20.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:20.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:20.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:20.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:20.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:20.917: INFO:
Nov 14 16:50:22.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:22.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:22.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:22.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
Nov 14 16:50:22.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:22.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:22.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:22.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:22.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:22.918: INFO:
Nov 14 16:50:24.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:24.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:24.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:24.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
Nov 14 16:50:24.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:24.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:24.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:24.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:24.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:24.918: INFO:
Nov 14 16:50:26.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:26.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:26.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:26.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
Nov 14 16:50:26.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:26.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:26.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:26.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:26.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:26.918: INFO:
Nov 14 16:50:28.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:28.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:28.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:28.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
Nov 14 16:50:28.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:28.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:28.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:28.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:28.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:28.916: INFO:
Nov 14 16:50:30.924: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:30.924: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:30.924: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:30.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
Nov 14 16:50:30.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:30.924: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:30.924: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:30.924: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:30.924: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:30.924: INFO:
Nov 14 16:50:32.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:32.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:32.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:32.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
Nov 14 16:50:32.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:32.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:32.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:32.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:32.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:32.920: INFO:
Nov 14 16:50:34.923: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:34.923: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:34.923: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:34.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
Nov 14 16:50:34.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:34.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:34.923: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:34.923: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:34.923: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:34.923: INFO:
Nov 14 16:50:36.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:36.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:36.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:36.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
Nov 14 16:50:36.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:36.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:36.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:36.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:36.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:36.916: INFO:
Nov 14 16:50:38.924: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:38.924: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:38.924: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:38.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
Nov 14 16:50:38.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:38.924: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:38.924: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:38.924: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:38.924: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:38.924: INFO:
Nov 14 16:50:40.922: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:40.922: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:40.922: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:40.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
Nov 14 16:50:40.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:40.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:40.922: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:40.922: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:40.922: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:40.922: INFO:
Nov 14 16:50:42.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:42.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:42.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:42.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
Nov 14 16:50:42.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:42.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:42.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:42.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:42.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:42.918: INFO:
Nov 14 16:50:44.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:44.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:44.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:44.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
Nov 14 16:50:44.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:44.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:44.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:44.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:44.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:44.919: INFO:
Nov 14 16:50:46.923: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:46.923: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:46.923: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:46.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
Nov 14 16:50:46.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:46.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:46.924: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:46.924: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:46.924: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:46.924: INFO:
Nov 14 16:50:48.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:48.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:48.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:48.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
Nov 14 16:50:48.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:48.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:48.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:48.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:48.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:48.917: INFO:
Nov 14 16:50:50.927: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:50.927: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:50.927: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:50.927: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
Nov 14 16:50:50.927: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:50.927: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:50.927: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:50.927: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:50.927: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:50.927: INFO:
Nov 14 16:50:52.923: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:52.923: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:52.923: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:52.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
Nov 14 16:50:52.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:52.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:52.923: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:52.923: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:52.923: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:52.923: INFO:
Nov 14 16:50:55.031: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:55.031: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:55.031: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:55.031: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
Nov 14 16:50:55.031: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:55.031: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:55.031: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:55.031: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:55.031: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:55.031: INFO:
Nov 14 16:50:56.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:56.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:56.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:56.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
Nov 14 16:50:56.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:56.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:56.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:56.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:56.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:56.916: INFO:
Nov 14 16:50:58.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:58.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:58.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:50:58.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
Nov 14 16:50:58.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:50:58.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:50:58.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:58.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:58.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:50:58.919: INFO:
Nov 14 16:51:00.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:00.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:00.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:00.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
Nov 14 16:51:00.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:00.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:00.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:00.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:00.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:00.919: INFO:
Nov 14 16:51:02.922: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:02.922: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:02.922: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:02.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
Nov 14 16:51:02.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:02.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:02.922: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:02.922: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:02.922: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:02.922: INFO:
Nov 14 16:51:04.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:04.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:04.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:04.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
Nov 14 16:51:04.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:04.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:04.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:04.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:04.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:04.920: INFO:
Nov 14 16:51:06.925: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:06.925: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:06.925: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:06.925: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
Nov 14 16:51:06.925: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:06.925: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:06.925: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:06.925: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:06.925: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:06.925: INFO:
Nov 14 16:51:08.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:08.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:08.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:08.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
Nov 14 16:51:08.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:08.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:08.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:08.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:08.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:08.920: INFO:
Nov 14 16:51:10.924: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:10.924: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:10.924: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:10.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
Nov 14 16:51:10.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:10.924: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:10.924: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:10.924: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:10.924: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:10.924: INFO:
Nov 14 16:51:12.926: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:12.926: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:12.926: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:12.926: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
Nov 14 16:51:12.926: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:12.926: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:12.926: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:12.926: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:12.926: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:12.926: INFO:
Nov 14 16:51:14.922: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:14.922: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:14.922: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:14.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
Nov 14 16:51:14.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:14.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:14.922: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:14.922: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:14.922: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:14.922: INFO:
Nov 14 16:51:16.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:16.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:16.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:16.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
Nov 14 16:51:16.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:16.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:16.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:16.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:16.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:16.920: INFO:
Nov 14 16:51:18.929: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:18.929: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:18.929: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:18.929: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
Nov 14 16:51:18.929: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:18.929: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:18.929: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:18.929: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:18.929: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:18.929: INFO:
Nov 14 16:51:20.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:20.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:20.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:20.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
Nov 14 16:51:20.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:20.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:20.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:20.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:20.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:20.920: INFO:
Nov 14 16:51:22.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:22.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:22.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:22.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
Nov 14 16:51:22.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:22.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:22.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:22.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:22.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:22.919: INFO:
Nov 14 16:51:24.924: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:24.924: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:24.924: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:24.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
Nov 14 16:51:24.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:24.924: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:24.924: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:24.924: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:24.924: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:24.924: INFO:
Nov 14 16:51:26.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:26.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:26.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:26.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
Nov 14 16:51:26.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:26.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:26.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:26.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:26.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:26.921: INFO:
Nov 14 16:51:28.922: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:28.922: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:28.922: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:28.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
Nov 14 16:51:28.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:28.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:28.922: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:28.922: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:28.922: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:28.922: INFO:
Nov 14 16:51:30.922: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:30.922: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:30.922: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:30.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
Nov 14 16:51:30.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:30.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:30.922: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:30.922: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:30.922: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:30.922: INFO:
Nov 14 16:51:32.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:32.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:32.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:32.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
Nov 14 16:51:32.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:32.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:32.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:32.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:32.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:32.920: INFO:
Nov 14 16:51:34.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:34.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:34.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:34.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
Nov 14 16:51:34.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:34.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:34.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:34.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:34.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:34.920: INFO:
Nov 14 16:51:36.923: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:36.923: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:36.923: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:36.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
Nov 14 16:51:36.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:36.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:36.923: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:36.923: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:36.923: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:36.923: INFO:
Nov 14 16:51:38.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:38.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:38.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:38.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
Nov 14 16:51:38.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:38.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:38.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:38.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:38.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:38.919: INFO:
Nov 14 16:51:40.923: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:40.923: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:40.923: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:40.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
Nov 14 16:51:40.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:40.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:40.923: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:40.923: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:40.923: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:40.923: INFO:
Nov 14 16:51:42.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:42.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:42.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:42.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
Nov 14 16:51:42.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:42.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:42.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:42.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:42.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:42.919: INFO:
Nov 14 16:51:44.927: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:44.927: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:44.927: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:44.927: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
Nov 14 16:51:44.927: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:44.927: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:44.927: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:44.927: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:44.927: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:44.927: INFO:
Nov 14 16:51:46.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:46.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:46.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:46.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
Nov 14 16:51:46.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:46.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:46.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:46.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:46.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:46.921: INFO:
Nov 14 16:51:48.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:48.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:48.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:48.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
Nov 14 16:51:48.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:48.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:48.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:48.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:48.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:48.921: INFO:
Nov 14 16:51:50.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:50.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:50.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:50.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
Nov 14 16:51:50.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:50.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:50.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:50.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:50.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:50.921: INFO:
Nov 14 16:51:52.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:52.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:52.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:52.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
Nov 14 16:51:52.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:52.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:52.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:52.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:52.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:52.920: INFO:
Nov 14 16:51:54.941: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:54.941: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:54.941: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:54.941: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
Nov 14 16:51:54.941: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:54.941: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:54.941: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:54.941: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:54.941: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:54.941: INFO:
Nov 14 16:51:56.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:56.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:56.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:56.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
Nov 14 16:51:56.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:56.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:56.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:56.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:56.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:56.918: INFO:
Nov 14 16:51:58.925: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:58.925: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:58.925: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:51:58.925: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
Nov 14 16:51:58.925: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:51:58.925: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:51:58.925: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:58.925: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:58.925: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:51:58.925: INFO:
Nov 14 16:52:00.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:00.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:00.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:00.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
Nov 14 16:52:00.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:00.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:00.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:00.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:00.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:00.920: INFO:
Nov 14 16:52:02.922: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:02.922: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:02.922: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:02.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
Nov 14 16:52:02.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:02.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:02.922: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:02.922: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:02.922: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:02.922: INFO:
Nov 14 16:52:04.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:04.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:04.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:04.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
Nov 14 16:52:04.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:04.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:04.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:04.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:04.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:04.921: INFO:
Nov 14 16:52:06.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:06.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:06.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:06.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
Nov 14 16:52:06.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:06.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:06.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:06.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:06.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:06.921: INFO:
Nov 14 16:52:08.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:08.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:08.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:08.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
Nov 14 16:52:08.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:08.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:08.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:08.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:08.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:08.917: INFO:
Nov 14 16:52:10.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:10.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:10.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:10.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
Nov 14 16:52:10.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:10.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:10.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:10.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:10.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:10.917: INFO:
Nov 14 16:52:12.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:12.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:12.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:12.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
Nov 14 16:52:12.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:12.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:12.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:12.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:12.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:12.921: INFO:
Nov 14 16:52:14.923: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:14.923: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:14.923: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:14.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
Nov 14 16:52:14.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:14.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:14.923: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:14.923: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:14.923: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:14.923: INFO:
Nov 14 16:52:16.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:16.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:16.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:16.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
Nov 14 16:52:16.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:16.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:16.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:16.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:16.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:16.916: INFO:
Nov 14 16:52:18.917: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:18.917: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:18.917: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:18.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
Nov 14 16:52:18.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:18.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:18.917: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:18.917: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:18.917: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:18.917: INFO:
Nov 14 16:52:20.924: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:20.924: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:20.924: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:20.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
Nov 14 16:52:20.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:20.924: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:20.924: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:20.924: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:20.924: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:20.924: INFO:
Nov 14 16:52:22.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:22.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:22.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:22.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
Nov 14 16:52:22.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:22.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:22.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:22.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:22.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:22.921: INFO:
Nov 14 16:52:24.925: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:24.925: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:24.925: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:24.925: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
Nov 14 16:52:24.925: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:24.926: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:24.926: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:24.926: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:24.926: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:24.926: INFO:
Nov 14 16:52:26.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:26.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:26.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:26.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
Nov 14 16:52:26.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:26.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:26.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:26.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:26.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:26.918: INFO:
Nov 14 16:52:28.923: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:28.923: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:28.923: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:28.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
Nov 14 16:52:28.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:28.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:28.923: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:28.923: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:28.923: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:28.923: INFO:
Nov 14 16:52:30.916: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:30.916: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:30.916: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:30.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
Nov 14 16:52:30.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:30.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:30.916: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:30.916: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:30.916: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:30.916: INFO:
Nov 14 16:52:32.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:32.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:32.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:32.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
Nov 14 16:52:32.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:32.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:32.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:32.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:32.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:32.921: INFO:
Nov 14 16:52:34.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:34.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:34.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:34.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
Nov 14 16:52:34.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:34.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:34.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:34.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:34.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:34.920: INFO:
Nov 14 16:52:36.923: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:36.923: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:36.923: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:36.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
Nov 14 16:52:36.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:36.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:36.923: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:36.923: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:36.923: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:36.923: INFO:
Nov 14 16:52:38.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:38.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:38.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:38.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
Nov 14 16:52:38.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:38.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:38.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:38.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:38.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:38.918: INFO:
Nov 14 16:52:40.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:40.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:40.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:40.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
Nov 14 16:52:40.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:40.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:40.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:40.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:40.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:40.921: INFO:
Nov 14 16:52:42.924: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:42.924: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:42.924: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:42.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
Nov 14 16:52:42.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:42.924: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:42.924: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:42.924: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:42.924: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:42.924: INFO:
Nov 14 16:52:44.927: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:44.927: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:44.927: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:44.927: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
Nov 14 16:52:44.927: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:44.927: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:44.927: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:44.927: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:44.927: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:44.927: INFO:
Nov 14 16:52:46.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:46.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:46.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:46.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
Nov 14 16:52:46.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:46.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:46.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:46.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:46.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:46.921: INFO:
Nov 14 16:52:48.926: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:48.926: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:48.926: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:48.926: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
Nov 14 16:52:48.927: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:48.927: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:48.927: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:48.927: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:48.927: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:48.927: INFO:
Nov 14 16:52:50.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:50.922: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:50.922: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:50.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
Nov 14 16:52:50.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:50.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:50.922: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:50.922: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:50.922: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:50.922: INFO:
Nov 14 16:52:52.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:52.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:52.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:52.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
Nov 14 16:52:52.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:52.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:52.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:52.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:52.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:52.921: INFO:
Nov 14 16:52:54.928: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:54.928: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:54.928: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:54.928: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
Nov 14 16:52:54.928: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:54.928: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:54.928: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:54.928: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:54.928: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:54.928: INFO:
Nov 14 16:52:56.922: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:56.922: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:56.922: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:56.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
Nov 14 16:52:56.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:56.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:56.922: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:56.922: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:56.922: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:56.922: INFO:
Nov 14 16:52:58.922: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:58.922: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:58.922: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:52:58.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
Nov 14 16:52:58.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:52:58.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:52:58.922: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:58.922: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:58.922: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:52:58.922: INFO:
Nov 14 16:53:00.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:00.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:00.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:00.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
Nov 14 16:53:00.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:00.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:00.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:00.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:00.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:00.920: INFO:
Nov 14 16:53:02.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:02.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:02.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:02.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
Nov 14 16:53:02.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:02.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:02.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:02.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:02.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:02.918: INFO:
Nov 14 16:53:04.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:04.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:04.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:04.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
Nov 14 16:53:04.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:04.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:04.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:04.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:04.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:04.921: INFO:
Nov 14 16:53:06.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:06.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:06.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:06.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
Nov 14 16:53:06.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:06.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:06.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:06.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:06.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:06.920: INFO:
Nov 14 16:53:08.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:08.919: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:08.919: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:08.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
Nov 14 16:53:08.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:08.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:08.919: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:08.919: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:08.919: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:08.919: INFO:
Nov 14 16:53:10.919: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:10.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:10.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:10.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
Nov 14 16:53:10.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:10.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:10.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:10.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:10.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:10.920: INFO:
Nov 14 16:53:12.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:12.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:12.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:12.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
Nov 14 16:53:12.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:12.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:12.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:12.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:12.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:12.920: INFO:
Nov 14 16:53:14.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:14.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:14.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:14.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
Nov 14 16:53:14.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:14.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:14.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:14.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:14.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:14.921: INFO:
Nov 14 16:53:16.927: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:16.927: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:16.927: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:16.927: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
Nov 14 16:53:16.927: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:16.927: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:16.927: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:16.927: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:16.927: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:16.927: INFO:
Nov 14 16:53:18.922: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:18.922: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:18.922: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:18.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
Nov 14 16:53:18.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:18.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:18.922: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:18.922: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:18.922: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:18.922: INFO:
Nov 14 16:53:20.925: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:20.925: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:20.925: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:20.925: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
Nov 14 16:53:20.925: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:20.925: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:20.925: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:20.925: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:20.925: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:20.925: INFO:
Nov 14 16:53:22.923: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:22.923: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:22.923: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:22.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
Nov 14 16:53:22.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:22.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:22.923: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:22.923: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:22.923: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:22.923: INFO:
Nov 14 16:53:24.933: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:24.933: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:24.933: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:24.933: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
Nov 14 16:53:24.933: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:24.933: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:24.933: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:24.933: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:24.933: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:24.933: INFO:
Nov 14 16:53:26.931: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:26.931: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:26.931: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:26.931: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
Nov 14 16:53:26.931: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:26.931: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:26.931: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:26.931: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:26.931: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:26.931: INFO:
Nov 14 16:53:28.933: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:28.933: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:28.933: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:28.933: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
Nov 14 16:53:28.933: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:28.933: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:28.933: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:28.933: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:28.933: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:28.933: INFO:
Nov 14 16:53:30.939: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:30.939: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:30.939: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:30.939: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
Nov 14 16:53:30.939: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:30.939: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:30.939: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:30.939: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:30.939: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:30.939: INFO:
Nov 14 16:53:32.937: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:32.937: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:32.937: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:32.937: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
Nov 14 16:53:32.937: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:32.937: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:32.937: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:32.937: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:32.937: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:32.937: INFO:
Nov 14 16:53:34.934: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:34.934: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:34.934: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:34.934: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
Nov 14 16:53:34.934: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:34.934: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:34.934: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:34.934: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:34.934: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:34.934: INFO:
Nov 14 16:53:36.934: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:36.934: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:36.934: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:36.934: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
Nov 14 16:53:36.934: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:36.934: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:36.934: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:36.934: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:36.934: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:36.934: INFO:
Nov 14 16:53:38.936: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:38.936: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:38.936: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:38.936: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
Nov 14 16:53:38.936: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:38.936: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:38.936: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:38.936: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:38.936: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:38.936: INFO:
Nov 14 16:53:40.937: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:40.937: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:40.937: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:40.937: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
Nov 14 16:53:40.937: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:40.937: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:40.937: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:40.937: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:40.937: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:40.937: INFO:
Nov 14 16:53:42.935: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:42.935: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:42.935: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:42.935: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
Nov 14 16:53:42.935: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:42.935: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:42.935: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:42.935: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:42.935: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:42.935: INFO:
Nov 14 16:53:44.935: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:44.936: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:44.936: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:44.936: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
Nov 14 16:53:44.936: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:44.936: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:44.936: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:44.936: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:44.936: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:44.936: INFO:
Nov 14 16:53:46.936: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:46.936: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:46.936: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:46.936: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
Nov 14 16:53:46.936: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:46.936: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:46.936: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:46.936: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:46.936: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:46.936: INFO:
Nov 14 16:53:48.932: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:48.932: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:48.932: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:48.932: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
Nov 14 16:53:48.932: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:48.932: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:48.932: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:48.932: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:48.932: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:48.932: INFO:
Nov 14 16:53:50.932: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:50.932: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:50.932: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:50.932: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
Nov 14 16:53:50.932: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:50.932: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:50.932: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:50.932: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:50.932: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:50.932: INFO:
Nov 14 16:53:52.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:52.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:52.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:52.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
Nov 14 16:53:52.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:52.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:52.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:52.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:52.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:52.921: INFO:
Nov 14 16:53:54.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:54.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:54.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:54.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
Nov 14 16:53:54.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:54.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:54.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:54.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:54.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:54.918: INFO:
Nov 14 16:53:56.922: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:56.922: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:56.922: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:56.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
Nov 14 16:53:56.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:56.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:56.922: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:56.922: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:56.922: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:56.922: INFO:
Nov 14 16:53:58.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:58.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:58.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:53:58.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
Nov 14 16:53:58.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:53:58.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:53:58.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:58.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:58.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:53:58.918: INFO:
Nov 14 16:54:00.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:00.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:00.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:00.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
Nov 14 16:54:00.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:54:00.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:54:00.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:00.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:00.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:00.921: INFO:
Nov 14 16:54:02.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:02.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:02.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:02.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
Nov 14 16:54:02.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:54:02.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:54:02.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:02.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:02.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:02.918: INFO:
Nov 14 16:54:04.925: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:04.925: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:04.925: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:04.925: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
Nov 14 16:54:04.925: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:54:04.925: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:54:04.925: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:04.925: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:04.925: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:04.925: INFO:
Nov 14 16:54:06.920: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:06.920: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:06.920: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:06.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
Nov 14 16:54:06.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:54:06.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:54:06.920: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:06.920: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:06.920: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:06.920: INFO:
Nov 14 16:54:08.923: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:08.923: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:08.923: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:08.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
Nov 14 16:54:08.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:54:08.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:54:08.923: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:08.923: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:08.923: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:08.923: INFO:
Nov 14 16:54:10.918: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:10.918: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:10.918: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:10.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Nov 14 16:54:10.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:54:10.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:54:10.918: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:10.918: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:10.918: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:10.918: INFO:
Nov 14 16:54:12.921: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:12.921: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:12.921: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:12.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Nov 14 16:54:12.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:54:12.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:54:12.921: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:12.921: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:12.921: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:12.921: INFO:
Nov 14 16:54:14.923: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:14.923: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:14.923: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:14.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 14 16:54:14.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:54:14.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:54:14.923: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:14.923: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:14.923: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:14.923: INFO:
Nov 14 16:54:15.049: INFO: The status of Pod kube-apiserver-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:15.049: INFO: The status of Pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:15.049: INFO: The status of Pod kube-scheduler-capz-conf-f16icx-control-plane-f7476 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 16:54:15.049: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 14 16:54:15.049: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 16:54:15.049: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:54:15.049: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:15.049: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:15.049: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:15.049: INFO:
�[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m11/14/22 16:54:15.049�[0m
�[1mSTEP:�[0m Found 125 events. �[38;5;243m11/14/22 16:54:15.097�[0m
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:31:35 +0000 UTC - event for etcd-capz-conf-f16icx-control-plane-f7476: {kubelet capz-conf-f16icx-control-plane-f7476} Pulled: Container image "registry.k8s.io/etcd:3.5.5-0" already present on machine
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:31:43 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-f16icx-control-plane-f7476_a131139d-8c23-4c7c-a26b-0967d5020159 became leader
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:31:44 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-f16icx-control-plane-f7476_fa704399-ce50-4cb2-8167-09a21b6f285e became leader
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:31:48 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-787d4945fb to 2
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:31:48 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-dp54r
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:31:48 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-dl5w4
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:31:48 +0000 UTC - event for coredns-787d4945fb-dl5w4: {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 16:54:15.098: INFO: At 2022-11-14 16:31:48 +0000 UTC - event for coredns-787d4945fb-dp54r: {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 16:54:15.098: INFO: At 2022-11-14 16:31:48 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-mhtxb
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:31:48 +0000 UTC - event for kube-proxy-mhtxb: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-mhtxb to capz-conf-f16icx-control-plane-f7476
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:31:49 +0000 UTC - event for kube-proxy-mhtxb: {kubelet capz-conf-f16icx-control-plane-f7476} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.79_62f74a8f14e815"
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:31:53 +0000 UTC - event for kube-proxy-mhtxb: {kubelet capz-conf-f16icx-control-plane-f7476} Started: Started container kube-proxy
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:31:53 +0000 UTC - event for kube-proxy-mhtxb: {kubelet capz-conf-f16icx-control-plane-f7476} Created: Created container kube-proxy
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:31:53 +0000 UTC - event for kube-proxy-mhtxb: {kubelet capz-conf-f16icx-control-plane-f7476} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.79_62f74a8f14e815" in 3.467738776s (3.467758077s including waiting)
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:06 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:06 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-44n4l
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:06 +0000 UTC - event for metrics-server-c9574f845-44n4l: {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 16:54:15.098: INFO: At 2022-11-14 16:32:08 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:08 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-qv5gv
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:08 +0000 UTC - event for calico-kube-controllers-657b584867-qv5gv: {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 16:54:15.098: INFO: At 2022-11-14 16:32:08 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-p8mdz
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:08 +0000 UTC - event for calico-node-p8mdz: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-p8mdz to capz-conf-f16icx-control-plane-f7476
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:09 +0000 UTC - event for calico-node-p8mdz: {kubelet capz-conf-f16icx-control-plane-f7476} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:16 +0000 UTC - event for calico-node-p8mdz: {kubelet capz-conf-f16icx-control-plane-f7476} Started: Started container upgrade-ipam
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:16 +0000 UTC - event for calico-node-p8mdz: {kubelet capz-conf-f16icx-control-plane-f7476} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 7.19669195s (7.19669855s including waiting)
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:16 +0000 UTC - event for calico-node-p8mdz: {kubelet capz-conf-f16icx-control-plane-f7476} Created: Created container upgrade-ipam
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:20 +0000 UTC - event for calico-node-p8mdz: {kubelet capz-conf-f16icx-control-plane-f7476} Started: Started container install-cni
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:20 +0000 UTC - event for calico-node-p8mdz: {kubelet capz-conf-f16icx-control-plane-f7476} Created: Created container install-cni
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:20 +0000 UTC - event for calico-node-p8mdz: {kubelet capz-conf-f16icx-control-plane-f7476} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:22 +0000 UTC - event for calico-kube-controllers-657b584867-qv5gv: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-qv5gv to capz-conf-f16icx-control-plane-f7476
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:22 +0000 UTC - event for coredns-787d4945fb-dl5w4: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-dl5w4 to capz-conf-f16icx-control-plane-f7476
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:22 +0000 UTC - event for coredns-787d4945fb-dp54r: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-dp54r to capz-conf-f16icx-control-plane-f7476
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:22 +0000 UTC - event for metrics-server-c9574f845-44n4l: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-44n4l to capz-conf-f16icx-control-plane-f7476
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:23 +0000 UTC - event for calico-kube-controllers-657b584867-qv5gv: {kubelet capz-conf-f16icx-control-plane-f7476} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "a8b8b53fc189d033a19117f006e0efb375f525d49ede034ff654d9742c348d89": 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 16:54:15.098: INFO: At 2022-11-14 16:32:23 +0000 UTC - event for calico-node-p8mdz: {kubelet capz-conf-f16icx-control-plane-f7476} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:23 +0000 UTC - event for coredns-787d4945fb-dl5w4: {kubelet capz-conf-f16icx-control-plane-f7476} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "5461b65064f7d5ce673294dfe7d21f7b34e32300665f53e623e182dc40ce5a35": 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 16:54:15.098: INFO: At 2022-11-14 16:32:23 +0000 UTC - event for coredns-787d4945fb-dp54r: {kubelet capz-conf-f16icx-control-plane-f7476} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "b24924cb182708392dca79068fa70107fa249360bfb54b46150f2714bb2f41bc": 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 16:54:15.098: INFO: At 2022-11-14 16:32:23 +0000 UTC - event for metrics-server-c9574f845-44n4l: {kubelet capz-conf-f16icx-control-plane-f7476} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "3c507092c2897c1ef1f1ec7544aa3d7f405c124915d74381508eea5e4c2470be": 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 16:54:15.098: INFO: At 2022-11-14 16:32:29 +0000 UTC - event for calico-node-p8mdz: {kubelet capz-conf-f16icx-control-plane-f7476} Created: Created container calico-node
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:29 +0000 UTC - event for calico-node-p8mdz: {kubelet capz-conf-f16icx-control-plane-f7476} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 6.771959439s (6.77197654s including waiting)
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:30 +0000 UTC - event for calico-node-p8mdz: {kubelet capz-conf-f16icx-control-plane-f7476} Started: Started container calico-node
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:30 +0000 UTC - event for calico-node-p8mdz: {kubelet capz-conf-f16icx-control-plane-f7476} 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 16:54:15.098: INFO: At 2022-11-14 16:32:35 +0000 UTC - event for calico-kube-controllers-657b584867-qv5gv: {kubelet capz-conf-f16icx-control-plane-f7476} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0"
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:36 +0000 UTC - event for metrics-server-c9574f845-44n4l: {kubelet capz-conf-f16icx-control-plane-f7476} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:39 +0000 UTC - event for coredns-787d4945fb-dl5w4: {kubelet capz-conf-f16icx-control-plane-f7476} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:40 +0000 UTC - event for coredns-787d4945fb-dl5w4: {kubelet capz-conf-f16icx-control-plane-f7476} Created: Created container coredns
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:40 +0000 UTC - event for coredns-787d4945fb-dl5w4: {kubelet capz-conf-f16icx-control-plane-f7476} Started: Started container coredns
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:40 +0000 UTC - event for coredns-787d4945fb-dp54r: {kubelet capz-conf-f16icx-control-plane-f7476} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:40 +0000 UTC - event for coredns-787d4945fb-dp54r: {kubelet capz-conf-f16icx-control-plane-f7476} Created: Created container coredns
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:40 +0000 UTC - event for coredns-787d4945fb-dp54r: {kubelet capz-conf-f16icx-control-plane-f7476} Started: Started container coredns
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:41 +0000 UTC - event for calico-kube-controllers-657b584867-qv5gv: {kubelet capz-conf-f16icx-control-plane-f7476} Started: Started container calico-kube-controllers
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:41 +0000 UTC - event for calico-kube-controllers-657b584867-qv5gv: {kubelet capz-conf-f16icx-control-plane-f7476} Created: Created container calico-kube-controllers
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:41 +0000 UTC - event for calico-kube-controllers-657b584867-qv5gv: {kubelet capz-conf-f16icx-control-plane-f7476} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 5.866724779s (5.866831277s including waiting)
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:41 +0000 UTC - event for coredns-787d4945fb-dl5w4: {kubelet capz-conf-f16icx-control-plane-f7476} Unhealthy: Readiness probe failed: Get "http://192.168.244.3:8181/ready": dial tcp 192.168.244.3:8181: connect: connection refused
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:41 +0000 UTC - event for coredns-787d4945fb-dp54r: {kubelet capz-conf-f16icx-control-plane-f7476} Unhealthy: Readiness probe failed: Get "http://192.168.244.4:8181/ready": dial tcp 192.168.244.4:8181: connect: connection refused
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:45 +0000 UTC - event for metrics-server-c9574f845-44n4l: {kubelet capz-conf-f16icx-control-plane-f7476} Started: Started container metrics-server
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:45 +0000 UTC - event for metrics-server-c9574f845-44n4l: {kubelet capz-conf-f16icx-control-plane-f7476} Created: Created container metrics-server
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:32:45 +0000 UTC - event for metrics-server-c9574f845-44n4l: {kubelet capz-conf-f16icx-control-plane-f7476} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 3.804348083s (8.411983259s including waiting)
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:07 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-n8r9c
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:07 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-zn2ld
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:07 +0000 UTC - event for calico-node-windows-n8r9c: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-n8r9c to capz-conf-7qbdc
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:07 +0000 UTC - event for calico-node-windows-zn2ld: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-zn2ld to capz-conf-gd96z
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:07 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-2k6q5
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:07 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-5jtzz
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:07 +0000 UTC - event for containerd-logger-2k6q5: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-2k6q5 to capz-conf-gd96z
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:07 +0000 UTC - event for containerd-logger-5jtzz: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-5jtzz to capz-conf-7qbdc
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:07 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-t2x8l
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:07 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-gfd79
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:07 +0000 UTC - event for kube-proxy-windows-gfd79: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-gfd79 to capz-conf-7qbdc
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:07 +0000 UTC - event for kube-proxy-windows-t2x8l: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-t2x8l to capz-conf-gd96z
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:09 +0000 UTC - event for calico-node-windows-n8r9c: {kubelet capz-conf-7qbdc} FailedMount: MountVolume.SetUp failed for volume "calico-static-rules" : failed to sync configmap cache: timed out waiting for the condition
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:09 +0000 UTC - event for containerd-logger-2k6q5: {kubelet capz-conf-gd96z} FailedMount: MountVolume.SetUp failed for volume "containerd-logger-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:09 +0000 UTC - event for kube-proxy-windows-gfd79: {kubelet capz-conf-7qbdc} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:24 +0000 UTC - event for calico-node-windows-n8r9c: {kubelet capz-conf-7qbdc} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:24 +0000 UTC - event for calico-node-windows-zn2ld: {kubelet capz-conf-gd96z} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:24 +0000 UTC - event for containerd-logger-2k6q5: {kubelet capz-conf-gd96z} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:24 +0000 UTC - event for containerd-logger-5jtzz: {kubelet capz-conf-7qbdc} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:24 +0000 UTC - event for kube-proxy-windows-gfd79: {kubelet capz-conf-7qbdc} Started: Started container kube-proxy
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:24 +0000 UTC - event for kube-proxy-windows-gfd79: {kubelet capz-conf-7qbdc} Created: Created container kube-proxy
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:24 +0000 UTC - event for kube-proxy-windows-gfd79: {kubelet capz-conf-7qbdc} Pulled: Container image "sigwindowstools/kube-proxy:v1.26.0-beta.0.65_8e48df13531802-calico-hostprocess" already present on machine
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:24 +0000 UTC - event for kube-proxy-windows-t2x8l: {kubelet capz-conf-gd96z} Created: Created container kube-proxy
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:24 +0000 UTC - event for kube-proxy-windows-t2x8l: {kubelet capz-conf-gd96z} Pulled: Container image "sigwindowstools/kube-proxy:v1.26.0-beta.0.65_8e48df13531802-calico-hostprocess" already present on machine
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:24 +0000 UTC - event for kube-proxy-windows-t2x8l: {kubelet capz-conf-gd96z} Started: Started container kube-proxy
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:27 +0000 UTC - event for containerd-logger-5jtzz: {kubelet capz-conf-7qbdc} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 3.1948929s (3.1948929s including waiting)
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:28 +0000 UTC - event for calico-node-windows-zn2ld: {kubelet capz-conf-gd96z} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 4.2834938s (4.2834938s including waiting)
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:28 +0000 UTC - event for calico-node-windows-zn2ld: {kubelet capz-conf-gd96z} Created: Created container install-cni
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:29 +0000 UTC - event for calico-node-windows-zn2ld: {kubelet capz-conf-gd96z} Started: Started container install-cni
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:30 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-s4227
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:30 +0000 UTC - event for csi-proxy-s4227: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-s4227 to capz-conf-gd96z
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:30 +0000 UTC - event for csi-proxy-s4227: {kubelet capz-conf-gd96z} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:32 +0000 UTC - event for calico-node-windows-n8r9c: {kubelet capz-conf-7qbdc} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 5.149003s (8.2928866s including waiting)
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:32 +0000 UTC - event for calico-node-windows-n8r9c: {kubelet capz-conf-7qbdc} Created: Created container install-cni
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:32 +0000 UTC - event for containerd-logger-2k6q5: {kubelet capz-conf-gd96z} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 3.6878899s (7.9515211s including waiting)
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:33 +0000 UTC - event for calico-node-windows-n8r9c: {kubelet capz-conf-7qbdc} Started: Started container install-cni
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:34 +0000 UTC - event for calico-node-windows-zn2ld: {kubelet capz-conf-gd96z} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:34 +0000 UTC - event for containerd-logger-5jtzz: {kubelet capz-conf-7qbdc} Started: Started container containerd-logger
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:34 +0000 UTC - event for containerd-logger-5jtzz: {kubelet capz-conf-7qbdc} Created: Created container containerd-logger
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:34 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-djjs7
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:34 +0000 UTC - event for csi-proxy-djjs7: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-djjs7 to capz-conf-7qbdc
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:35 +0000 UTC - event for csi-proxy-djjs7: {kubelet capz-conf-7qbdc} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:38 +0000 UTC - event for calico-node-windows-n8r9c: {kubelet capz-conf-7qbdc} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:38 +0000 UTC - event for containerd-logger-2k6q5: {kubelet capz-conf-gd96z} Created: Created container containerd-logger
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:38 +0000 UTC - event for containerd-logger-2k6q5: {kubelet capz-conf-gd96z} Started: Started container containerd-logger
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:47 +0000 UTC - event for csi-proxy-s4227: {kubelet capz-conf-gd96z} Created: Created container csi-proxy
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:47 +0000 UTC - event for csi-proxy-s4227: {kubelet capz-conf-gd96z} Started: Started container csi-proxy
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:47 +0000 UTC - event for csi-proxy-s4227: {kubelet capz-conf-gd96z} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 14.6585329s (16.1619113s including waiting)
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:49 +0000 UTC - event for csi-proxy-djjs7: {kubelet capz-conf-7qbdc} Started: Started container csi-proxy
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:49 +0000 UTC - event for csi-proxy-djjs7: {kubelet capz-conf-7qbdc} Created: Created container csi-proxy
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:49 +0000 UTC - event for csi-proxy-djjs7: {kubelet capz-conf-7qbdc} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 13.7515319s (13.7515319s including waiting)
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:50 +0000 UTC - event for calico-node-windows-zn2ld: {kubelet capz-conf-gd96z} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 229.4957ms (229.4957ms including waiting)
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:50 +0000 UTC - event for calico-node-windows-zn2ld: {kubelet capz-conf-gd96z} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:50 +0000 UTC - event for calico-node-windows-zn2ld: {kubelet capz-conf-gd96z} Started: Started container calico-node-startup
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:50 +0000 UTC - event for calico-node-windows-zn2ld: {kubelet capz-conf-gd96z} Created: Created container calico-node-startup
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:50 +0000 UTC - event for calico-node-windows-zn2ld: {kubelet capz-conf-gd96z} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 3.3908295s (15.6792517s including waiting)
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:52 +0000 UTC - event for calico-node-windows-n8r9c: {kubelet capz-conf-7qbdc} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:52 +0000 UTC - event for calico-node-windows-n8r9c: {kubelet capz-conf-7qbdc} Created: Created container calico-node-startup
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:52 +0000 UTC - event for calico-node-windows-n8r9c: {kubelet capz-conf-7qbdc} Started: Started container calico-node-startup
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:52 +0000 UTC - event for calico-node-windows-n8r9c: {kubelet capz-conf-7qbdc} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 3.0622449s (13.9911406s including waiting)
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:52 +0000 UTC - event for calico-node-windows-n8r9c: {kubelet capz-conf-7qbdc} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 248.4948ms (248.4948ms including waiting)
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:56 +0000 UTC - event for calico-node-windows-zn2ld: {kubelet capz-conf-gd96z} Started: Started container calico-node-felix
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:56 +0000 UTC - event for calico-node-windows-zn2ld: {kubelet capz-conf-gd96z} Created: Created container calico-node-felix
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:58 +0000 UTC - event for calico-node-windows-n8r9c: {kubelet capz-conf-7qbdc} Created: Created container calico-node-felix
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:43:58 +0000 UTC - event for calico-node-windows-n8r9c: {kubelet capz-conf-7qbdc} Started: Started container calico-node-felix
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:44:17 +0000 UTC - event for calico-node-windows-zn2ld: {kubelet capz-conf-gd96z} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 203.51ms (203.51ms including waiting)
Nov 14 16:54:15.098: INFO: At 2022-11-14 16:44:19 +0000 UTC - event for calico-node-windows-n8r9c: {kubelet capz-conf-7qbdc} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 227.4976ms (227.4976ms including waiting)
Nov 14 16:54:15.149: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 16:54:15.149: INFO: calico-kube-controllers-657b584867-qv5gv capz-conf-f16icx-control-plane-f7476 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:22 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:43 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:43 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:22 +0000 UTC }]
Nov 14 16:54:15.149: INFO: calico-node-p8mdz capz-conf-f16icx-control-plane-f7476 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:23 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:39 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:39 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:08 +0000 UTC }]
Nov 14 16:54:15.149: INFO: calico-node-windows-n8r9c capz-conf-7qbdc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:38 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:44:25 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:44:25 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:07 +0000 UTC }]
Nov 14 16:54:15.150: INFO: calico-node-windows-zn2ld capz-conf-gd96z Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:34 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:44:23 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:44:23 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:07 +0000 UTC }]
Nov 14 16:54:15.150: INFO: containerd-logger-2k6q5 capz-conf-gd96z Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:08 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:39 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:39 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:07 +0000 UTC }]
Nov 14 16:54:15.150: INFO: containerd-logger-5jtzz capz-conf-7qbdc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:08 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:35 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:35 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:07 +0000 UTC }]
Nov 14 16:54:15.150: INFO: coredns-787d4945fb-dl5w4 capz-conf-f16icx-control-plane-f7476 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:22 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:42 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:42 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:22 +0000 UTC }]
Nov 14 16:54:15.150: INFO: coredns-787d4945fb-dp54r capz-conf-f16icx-control-plane-f7476 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:22 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:42 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:42 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:22 +0000 UTC }]
Nov 14 16:54:15.150: INFO: csi-proxy-djjs7 capz-conf-7qbdc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:34 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:50 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:50 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:34 +0000 UTC }]
Nov 14 16:54:15.150: INFO: csi-proxy-s4227 capz-conf-gd96z Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:30 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:47 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:47 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:30 +0000 UTC }]
Nov 14 16:54:15.150: INFO: etcd-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:31:47 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:31:52 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:31:52 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:31:47 +0000 UTC }]
Nov 14 16:54:15.150: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:15.150: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:15.150: INFO: kube-proxy-mhtxb capz-conf-f16icx-control-plane-f7476 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:31:48 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:31:54 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:31:54 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:31:48 +0000 UTC }]
Nov 14 16:54:15.150: INFO: kube-proxy-windows-gfd79 capz-conf-7qbdc Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:08 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:24 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:24 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:07 +0000 UTC }]
Nov 14 16:54:15.150: INFO: kube-proxy-windows-t2x8l capz-conf-gd96z Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:08 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:25 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:25 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:43:07 +0000 UTC }]
Nov 14 16:54:15.150: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Nov 14 16:54:15.150: INFO: metrics-server-c9574f845-44n4l capz-conf-f16icx-control-plane-f7476 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:22 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:33:13 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:33:13 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 16:32:22 +0000 UTC }]
Nov 14 16:54:15.150: INFO:
Nov 14 16:54:15.641: INFO:
Logging node info for node capz-conf-7qbdc
Nov 14 16:54:15.832: INFO: Node Info: &Node{ObjectMeta:{capz-conf-7qbdc 8a00ef71-c619-49c9-812e-186e075a6659 2237 0 2022-11-14 16:43: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:eastus2 failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-7qbdc kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:eastus2 topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-f16icx cluster.x-k8s.io/cluster-namespace:capz-conf-f16icx cluster.x-k8s.io/machine:capz-conf-f16icx-md-win-5f4575986c-sgx5r cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-f16icx-md-win-5f4575986c 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.101.65 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:8b:ab:27 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet.exe Update v1 2022-11-14 16:43: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 16:43:08 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kube-controller-manager Update v1 2022-11-14 16:43:34 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-14 16:44:05 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {Go-http-client Update v1 2022-11-14 16:44:16 +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 16:49:15 +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-f16icx/providers/Microsoft.Compute/virtualMachines/capz-conf-7qbdc,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 16:49:15 +0000 UTC,LastTransitionTime:2022-11-14 16:43:07 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-14 16:49:15 +0000 UTC,LastTransitionTime:2022-11-14 16:43:07 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-14 16:49:15 +0000 UTC,LastTransitionTime:2022-11-14 16:43:07 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-14 16:49:15 +0000 UTC,LastTransitionTime:2022-11-14 16:43:34 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-7qbdc,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-7qbdc,SystemUUID:A5501399-A96F-4524-9C38-B83344272EC9,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.26.0-beta.0.79+62f74a8f14e815-dirty,KubeProxyVersion:v1.26.0-beta.0.79+62f74a8f14e815-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 16:54:15.833: INFO:
Logging kubelet events for node capz-conf-7qbdc
Nov 14 16:54:16.030: INFO:
Logging pods the kubelet thinks is on node capz-conf-7qbdc
Nov 14 16:54:16.247: INFO: calico-node-windows-n8r9c started at 2022-11-14 16:43:08 +0000 UTC (1+2 container statuses recorded)
Nov 14 16:54:16.247: INFO: Init container install-cni ready: true, restart count 0
Nov 14 16:54:16.247: INFO: Container calico-node-felix ready: true, restart count 1
Nov 14 16:54:16.247: INFO: Container calico-node-startup ready: true, restart count 0
Nov 14 16:54:16.247: INFO: containerd-logger-5jtzz started at 2022-11-14 16:43:08 +0000 UTC (0+1 container statuses recorded)
Nov 14 16:54:16.247: INFO: Container containerd-logger ready: true, restart count 0
Nov 14 16:54:16.247: INFO: kube-proxy-windows-gfd79 started at 2022-11-14 16:43:08 +0000 UTC (0+1 container statuses recorded)
Nov 14 16:54:16.247: INFO: Container kube-proxy ready: true, restart count 0
Nov 14 16:54:16.247: INFO: csi-proxy-djjs7 started at 2022-11-14 16:43:34 +0000 UTC (0+1 container statuses recorded)
Nov 14 16:54:16.247: INFO: Container csi-proxy ready: true, restart count 0
Nov 14 16:54:16.872: INFO:
Latency metrics for node capz-conf-7qbdc
Nov 14 16:54:16.873: INFO:
Logging node info for node capz-conf-f16icx-control-plane-f7476
Nov 14 16:54:17.033: INFO: Node Info: &Node{ObjectMeta:{capz-conf-f16icx-control-plane-f7476 3079273b-6ff7-4fcc-83ef-57d7028a911c 2586 0 2022-11-14 16:31:42 +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:eastus2 failure-domain.beta.kubernetes.io/zone:eastus2-3 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-f16icx-control-plane-f7476 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:eastus2 topology.kubernetes.io/zone:eastus2-3] map[cluster.x-k8s.io/cluster-name:capz-conf-f16icx cluster.x-k8s.io/cluster-namespace:capz-conf-f16icx cluster.x-k8s.io/machine:capz-conf-f16icx-control-plane-kr6dh cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-f16icx-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.244.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2022-11-14 16:31:42 +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 16:31:45 +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 16:32:05 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kube-controller-manager Update v1 2022-11-14 16:32:22 +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 16:32:30 +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 16:53:09 +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-f16icx/providers/Microsoft.Compute/virtualMachines/capz-conf-f16icx-control-plane-f7476,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 16:32:30 +0000 UTC,LastTransitionTime:2022-11-14 16:32:30 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-14 16:53:09 +0000 UTC,LastTransitionTime:2022-11-14 16:31:27 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-14 16:53:09 +0000 UTC,LastTransitionTime:2022-11-14 16:31:27 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-14 16:53:09 +0000 UTC,LastTransitionTime:2022-11-14 16:31:27 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-14 16:53:09 +0000 UTC,LastTransitionTime:2022-11-14 16:32:22 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-f16icx-control-plane-f7476,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:062b6c610c8549d89e84de58b3c8776f,SystemUUID:50f8afe6-6521-9b4b-b5ad-26fc4809ef86,BootID:9175708e-68e8-423b-b079-b16befa15d1b,KernelVersion:5.4.0-1091-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.26.0-beta.0.79+62f74a8f14e815,KubeProxyVersion:v1.26.0-beta.0.79+62f74a8f14e815,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:e9921fbd2a1f64fca935a40c30be9af28013921b3a99c772ccddab42726b2c12 capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.79_62f74a8f14e815],SizeBytes:21533067,},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 16:54:17.033: INFO:
Logging kubelet events for node capz-conf-f16icx-control-plane-f7476
Nov 14 16:54:17.230: INFO:
Logging pods the kubelet thinks is on node capz-conf-f16icx-control-plane-f7476
Nov 14 16:54:17.463: INFO: calico-node-p8mdz started at 2022-11-14 16:32:08 +0000 UTC (2+1 container statuses recorded)
Nov 14 16:54:17.463: INFO: Init container upgrade-ipam ready: true, restart count 0
Nov 14 16:54:17.463: INFO: Init container install-cni ready: true, restart count 0
Nov 14 16:54:17.463: INFO: Container calico-node ready: true, restart count 0
Nov 14 16:54:17.463: INFO: coredns-787d4945fb-dl5w4 started at 2022-11-14 16:32:22 +0000 UTC (0+1 container statuses recorded)
Nov 14 16:54:17.463: INFO: Container coredns ready: true, restart count 0
Nov 14 16:54:17.463: INFO: calico-kube-controllers-657b584867-qv5gv started at 2022-11-14 16:32:22 +0000 UTC (0+1 container statuses recorded)
Nov 14 16:54:17.463: INFO: Container calico-kube-controllers ready: true, restart count 0
Nov 14 16:54:17.463: INFO: kube-controller-manager-capz-conf-f16icx-control-plane-f7476 started at <nil> (0+0 container statuses recorded)
Nov 14 16:54:17.463: INFO: kube-proxy-mhtxb started at 2022-11-14 16:31:48 +0000 UTC (0+1 container statuses recorded)
Nov 14 16:54:17.463: INFO: Container kube-proxy ready: true, restart count 0
Nov 14 16:54:17.463: INFO: kube-scheduler-capz-conf-f16icx-control-plane-f7476 started at <nil> (0+0 container statuses recorded)
Nov 14 16:54:17.463: INFO: metrics-server-c9574f845-44n4l started at 2022-11-14 16:32:22 +0000 UTC (0+1 container statuses recorded)
Nov 14 16:54:17.463: INFO: Container metrics-server ready: true, restart count 0
Nov 14 16:54:17.463: INFO: coredns-787d4945fb-dp54r started at 2022-11-14 16:32:22 +0000 UTC (0+1 container statuses recorded)
Nov 14 16:54:17.463: INFO: Container coredns ready: true, restart count 0
Nov 14 16:54:17.463: INFO: etcd-capz-conf-f16icx-control-plane-f7476 started at 2022-11-14 16:31:47 +0000 UTC (0+1 container statuses recorded)
Nov 14 16:54:17.463: INFO: Container etcd ready: true, restart count 0
Nov 14 16:54:17.463: INFO: kube-apiserver-capz-conf-f16icx-control-plane-f7476 started at <nil> (0+0 container statuses recorded)
Nov 14 16:54:18.084: INFO:
Latency metrics for node capz-conf-f16icx-control-plane-f7476
Nov 14 16:54:18.084: INFO:
Logging node info for node capz-conf-gd96z
Nov 14 16:54:18.229: INFO: Node Info: &Node{ObjectMeta:{capz-conf-gd96z 2d1f17d3-def9-41e3-b439-959d8a4c10f6 2238 0 2022-11-14 16:43: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:eastus2 failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-gd96z kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:eastus2 topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-f16icx cluster.x-k8s.io/cluster-namespace:capz-conf-f16icx cluster.x-k8s.io/machine:capz-conf-f16icx-md-win-5f4575986c-dqfvf cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-f16icx-md-win-5f4575986c 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.169.193 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:70:f7:cc volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-14 16:43:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-14 16:43: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":{}}} } {kube-controller-manager Update v1 2022-11-14 16:43:30 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-14 16:44:07 +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 16:44:14 +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 16:49:16 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-f16icx/providers/Microsoft.Compute/virtualMachines/capz-conf-gd96z,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 16:49:16 +0000 UTC,LastTransitionTime:2022-11-14 16:43:07 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-14 16:49:16 +0000 UTC,LastTransitionTime:2022-11-14 16:43:07 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-14 16:49:16 +0000 UTC,LastTransitionTime:2022-11-14 16:43:07 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-14 16:49:16 +0000 UTC,LastTransitionTime:2022-11-14 16:43:30 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-gd96z,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-gd96z,SystemUUID:98D1F9A5-820F-4294-B726-1C8C6CD1EB60,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.26.0-beta.0.79+62f74a8f14e815-dirty,KubeProxyVersion:v1.26.0-beta.0.79+62f74a8f14e815-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 16:54:18.230: INFO:
Logging kubelet events for node capz-conf-gd96z
Nov 14 16:54:18.429: INFO:
Logging pods the kubelet thinks is on node capz-conf-gd96z
Nov 14 16:54:18.634: INFO: csi-proxy-s4227 started at 2022-11-14 16:43:30 +0000 UTC (0+1 container statuses recorded)
Nov 14 16:54:18.634: INFO: Container csi-proxy ready: true, restart count 0
Nov 14 16:54:18.634: INFO: kube-proxy-windows-t2x8l started at 2022-11-14 16:43:08 +0000 UTC (0+1 container statuses recorded)
Nov 14 16:54:18.634: INFO: Container kube-proxy ready: true, restart count 0
Nov 14 16:54:18.634: INFO: calico-node-windows-zn2ld started at 2022-11-14 16:43:08 +0000 UTC (1+2 container statuses recorded)
Nov 14 16:54:18.634: INFO: Init container install-cni ready: true, restart count 0
Nov 14 16:54:18.634: INFO: Container calico-node-felix ready: true, restart count 1
Nov 14 16:54:18.634: INFO: Container calico-node-startup ready: true, restart count 0
Nov 14 16:54:18.634: INFO: containerd-logger-2k6q5 started at 2022-11-14 16:43:08 +0000 UTC (0+1 container statuses recorded)
Nov 14 16:54:18.634: INFO: Container containerd-logger ready: true, restart count 0
Nov 14 16:54:19.271: INFO:
Latency metrics for node capz-conf-gd96z
Nov 14 16:54:19.443: INFO: Running kubectl logs on non-ready containers in kube-system
Nov 14 16:54:19.830: INFO: Failed to get logs of pod kube-apiserver-capz-conf-f16icx-control-plane-f7476, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-f16icx-control-plane-f7476)
Nov 14 16:54:19.830: INFO: Logs of kube-system/kube-apiserver-capz-conf-f16icx-control-plane-f7476:kube-apiserver on node capz-conf-f16icx-control-plane-f7476
Nov 14 16:54:19.830: INFO: : STARTLOG
ENDLOG for container kube-system:kube-apiserver-capz-conf-f16icx-control-plane-f7476:kube-apiserver
Nov 14 16:54:20.230: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-f16icx-control-plane-f7476, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-f16icx-control-plane-f7476)
Nov 14 16:54:20.230: INFO: Logs of kube-system/kube-controller-manager-capz-conf-f16icx-control-plane-f7476:kube-controller-manager on node capz-conf-f16icx-control-plane-f7476
Nov 14 16:54:20.230: INFO: : STARTLOG
ENDLOG for container kube-system:kube-controller-manager-capz-conf-f16icx-control-plane-f7476:kube-controller-manager
Nov 14 16:54:20.630: INFO: Failed to get logs of pod kube-scheduler-capz-conf-f16icx-control-plane-f7476, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-f16icx-control-plane-f7476)
Nov 14 16:54:20.630: INFO: Logs of kube-system/kube-scheduler-capz-conf-f16icx-control-plane-f7476:kube-scheduler on node capz-conf-f16icx-control-plane-f7476
Nov 14 16:54:20.630: INFO: : STARTLOG
ENDLOG for container kube-system:kube-scheduler-capz-conf-f16icx-control-plane-f7476:kube-scheduler
Nov 14 16:54:20.630: 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-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
kube-controller-manager-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
kube-scheduler-capz-conf-f16icx-control-plane-f7476 capz-conf-f16icx-control-plane-f7476 Pending []
Full Stack Trace
k8s.io/kubernetes/test/e2e.setupSuite({0x7f0024e448d8, 0xc001264400})
test/e2e/e2e.go:249 +0x5bf
k8s.io/kubernetes/test/e2e.glob..func1({0x7f0024e448d8, 0xc001264400})
test/e2e/e2e.go:81 +0xaa
reflect.Value.call({0x6856240?, 0x78af028?, 0x13?}, {0x75d139a, 0x4}, {0xc000cb8f38, 0x1, 0x1?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x6856240?, 0x78af028?, 0x26c35ed?}, {0xc0000a2738?, 0x2651b67?, 0xc0000a2720?})
/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