PR #112923 pull-kubernetes-e2e-capz-windows-containerd #1592222659880423424
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 | 1h4m |
| Revision | b27e4de3c07aacf6a1409101177d8666b15451b6 |
| Refs |
112923 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:249
k8s.io/kubernetes/test/e2e.setupSuite({0x7f63e00e1db8, 0xc0022caec0})
test/e2e/e2e.go:249 +0x5bf
k8s.io/kubernetes/test/e2e.glob..func1({0x7f63e00e1db8, 0xc0022caec0})
test/e2e/e2e.go:81 +0xaa
reflect.Value.call({0x6855240?, 0x78ae028?, 0x0?}, {0x75d039a, 0x4}, {0xc000b61f38, 0x1, 0x0?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x6855240?, 0x78ae028?, 0x0?}, {0xc000b61f38?, 0x0?, 0x0?})
/usr/local/go/src/reflect/value.go:368 +0xbc
[SynchronizedBeforeSuite] TOP-LEVEL
test/e2e/e2e.go:77
Nov 14 19:11:39.552: INFO: >>> kubeConfig: /tmp/kubeconfig
Nov 14 19:11:39.556: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Nov 14 19:11:39.736: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Nov 14 19:11:39.868: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:39.868: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:39.868: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:39.868: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Nov 14 19:11:39.868: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:11:39.868: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:11:39.868: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:39.868: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:39.868: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:39.868: INFO:
Nov 14 19:11:42.001: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:42.001: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:42.001: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:42.001: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Nov 14 19:11:42.001: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:11:42.001: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:11:42.001: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:42.001: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:42.001: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:42.001: INFO:
Nov 14 19:11:44.000: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:44.000: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:44.000: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:44.000: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Nov 14 19:11:44.000: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:11:44.000: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:11:44.000: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:44.000: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:44.000: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:44.000: INFO:
Nov 14 19:11:45.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:45.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:45.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:45.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Nov 14 19:11:45.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:11:45.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:11:45.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:45.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:45.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:45.999: INFO:
Nov 14 19:11:48.003: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:48.003: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:48.003: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:48.003: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Nov 14 19:11:48.003: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:11:48.003: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:11:48.003: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:48.003: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:48.003: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:48.003: INFO:
Nov 14 19:11:50.005: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:50.005: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:50.005: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:50.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Nov 14 19:11:50.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:11:50.005: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:11:50.005: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:50.005: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:50.005: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:50.005: INFO:
Nov 14 19:11:52.001: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:52.001: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:52.001: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:52.001: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Nov 14 19:11:52.001: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:11:52.001: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:11:52.001: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:52.001: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:52.001: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:52.001: INFO:
Nov 14 19:11:54.002: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:54.002: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:54.002: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:54.002: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Nov 14 19:11:54.002: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:11:54.002: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:11:54.002: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:54.002: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:54.002: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:54.002: INFO:
Nov 14 19:11:56.001: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:56.001: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:56.001: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:56.001: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Nov 14 19:11:56.001: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:11:56.001: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:11:56.001: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:56.001: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:56.001: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:56.001: INFO:
Nov 14 19:11:57.998: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:57.998: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:57.998: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:11:57.998: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Nov 14 19:11:57.998: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:11:57.998: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:11:57.998: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:57.998: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:57.998: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:11:57.998: INFO:
Nov 14 19:12:00.003: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:00.003: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:00.003: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:00.003: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Nov 14 19:12:00.003: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:00.003: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:00.003: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:00.003: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:00.003: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:00.003: INFO:
Nov 14 19:12:01.998: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:01.998: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:01.998: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:01.998: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Nov 14 19:12:01.998: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:01.998: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:01.998: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:01.998: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:01.998: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:01.998: INFO:
Nov 14 19:12:03.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:03.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:03.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:03.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Nov 14 19:12:03.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:03.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:03.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:03.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:03.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:03.999: INFO:
Nov 14 19:12:06.002: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:06.002: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:06.002: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:06.002: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Nov 14 19:12:06.002: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:06.002: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:06.002: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:06.002: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:06.002: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:06.002: INFO:
Nov 14 19:12:08.000: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:08.000: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:08.000: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:08.000: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Nov 14 19:12:08.000: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:08.000: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:08.000: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:08.000: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:08.000: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:08.000: INFO:
Nov 14 19:12:10.010: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:10.010: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:10.010: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:10.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
Nov 14 19:12:10.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:10.010: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:10.010: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:10.010: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:10.010: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:10.010: INFO:
Nov 14 19:12:12.003: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:12.003: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:12.003: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:12.003: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
Nov 14 19:12:12.003: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:12.003: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:12.003: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:12.003: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:12.003: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:12.003: INFO:
Nov 14 19:12:14.008: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:14.008: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:14.008: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:14.009: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
Nov 14 19:12:14.009: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:14.009: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:14.009: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:14.009: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:14.009: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:14.009: INFO:
Nov 14 19:12:16.005: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:16.005: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:16.005: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:16.005: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
Nov 14 19:12:16.005: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:16.005: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:16.005: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:16.005: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:16.005: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:16.005: INFO:
Nov 14 19:12:18.001: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:18.001: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:18.001: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:18.001: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
Nov 14 19:12:18.001: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:18.001: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:18.001: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:18.001: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:18.001: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:18.001: INFO:
Nov 14 19:12:20.000: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:20.000: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:20.000: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:20.000: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
Nov 14 19:12:20.000: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:20.000: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:20.000: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:20.000: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:20.000: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:20.000: INFO:
Nov 14 19:12:21.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:21.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:21.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:21.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
Nov 14 19:12:21.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:21.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:21.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:21.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:21.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:21.999: INFO:
Nov 14 19:12:23.998: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:23.998: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:23.998: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:23.998: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
Nov 14 19:12:23.998: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:23.998: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:23.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:23.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:23.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:23.999: INFO:
Nov 14 19:12:25.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:25.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:25.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:25.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
Nov 14 19:12:25.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:25.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:25.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:25.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:25.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:25.999: INFO:
Nov 14 19:12:27.997: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:27.997: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:27.997: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:27.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
Nov 14 19:12:27.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:27.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:27.997: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:27.997: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:27.997: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:27.997: INFO:
Nov 14 19:12:29.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:29.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:29.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:29.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
Nov 14 19:12:29.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:29.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:29.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:29.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:29.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:29.999: INFO:
Nov 14 19:12:31.996: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:31.996: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:31.996: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:31.996: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
Nov 14 19:12:31.996: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:31.996: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:31.996: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:31.996: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:31.996: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:31.996: INFO:
Nov 14 19:12:34.002: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:34.002: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:34.002: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:34.002: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
Nov 14 19:12:34.002: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:34.002: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:34.002: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:34.002: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:34.002: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:34.002: INFO:
Nov 14 19:12:35.998: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:35.998: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:35.998: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:35.998: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
Nov 14 19:12:35.998: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:35.998: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:35.998: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:35.998: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:35.998: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:35.998: INFO:
Nov 14 19:12:37.998: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:37.998: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:37.998: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:37.998: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
Nov 14 19:12:37.998: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:37.998: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:37.998: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:37.998: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:37.998: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:37.998: INFO:
Nov 14 19:12:39.998: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:39.998: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:39.998: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:39.998: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
Nov 14 19:12:39.998: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:39.998: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:39.998: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:39.998: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:39.998: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:39.998: INFO:
Nov 14 19:12:41.998: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:41.998: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:41.998: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:41.998: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
Nov 14 19:12:41.998: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:41.998: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:41.998: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:41.998: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:41.998: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:41.998: INFO:
Nov 14 19:12:43.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:43.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:43.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:43.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
Nov 14 19:12:43.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:43.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:43.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:43.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:43.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:43.999: INFO:
Nov 14 19:12:45.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:45.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:45.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:45.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
Nov 14 19:12:45.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:45.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:45.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:45.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:45.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:45.999: INFO:
Nov 14 19:12:47.998: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:47.998: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:47.998: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:47.998: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
Nov 14 19:12:47.998: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:47.998: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:47.998: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:47.998: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:47.998: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:47.998: INFO:
Nov 14 19:12:50.002: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:50.002: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:50.002: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:50.002: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
Nov 14 19:12:50.002: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:50.002: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:50.002: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:50.002: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:50.002: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:50.002: INFO:
Nov 14 19:12:52.011: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:52.011: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:52.011: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:52.011: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
Nov 14 19:12:52.011: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:52.011: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:52.011: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:52.011: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:52.011: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:52.011: INFO:
Nov 14 19:12:53.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:53.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:53.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:53.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
Nov 14 19:12:53.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:53.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:53.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:53.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:53.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:53.999: INFO:
Nov 14 19:12:55.997: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:55.997: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:55.997: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:55.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
Nov 14 19:12:55.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:55.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:55.997: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:55.997: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:55.997: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:55.997: INFO:
Nov 14 19:12:57.997: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:57.997: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:57.997: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:12:57.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
Nov 14 19:12:57.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:12:57.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:12:57.997: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:57.997: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:57.997: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:12:57.997: INFO:
Nov 14 19:13:00.001: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:00.001: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:00.001: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:00.001: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
Nov 14 19:13:00.001: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:00.001: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:00.001: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:00.001: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:00.001: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:00.001: INFO:
Nov 14 19:13:02.002: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:02.002: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:02.002: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:02.002: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
Nov 14 19:13:02.002: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:02.002: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:02.002: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:02.002: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:02.002: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:02.002: INFO:
Nov 14 19:13:03.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:03.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:03.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:03.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
Nov 14 19:13:03.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:03.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:03.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:03.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:03.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:03.999: INFO:
Nov 14 19:13:05.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:05.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:05.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:05.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
Nov 14 19:13:05.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:05.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:05.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:05.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:05.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:05.999: INFO:
Nov 14 19:13:07.997: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:07.997: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:07.997: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:07.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
Nov 14 19:13:07.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:07.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:07.997: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:07.997: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:07.997: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:07.997: INFO:
Nov 14 19:13:09.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:09.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:09.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:09.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
Nov 14 19:13:09.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:09.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:09.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:09.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:09.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:09.999: INFO:
Nov 14 19:13:11.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:11.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:11.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:11.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
Nov 14 19:13:11.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:11.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:11.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:11.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:11.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:11.999: INFO:
Nov 14 19:13:14.002: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:14.002: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:14.002: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:14.002: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
Nov 14 19:13:14.002: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:14.002: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:14.002: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:14.002: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:14.002: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:14.002: INFO:
Nov 14 19:13:15.998: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:15.998: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:15.998: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:15.998: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
Nov 14 19:13:15.998: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:15.998: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:15.998: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:15.998: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:15.998: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:15.998: INFO:
Nov 14 19:13:17.997: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:17.997: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:17.997: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:17.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
Nov 14 19:13:17.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:17.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:17.997: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:17.997: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:17.997: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:17.997: INFO:
Nov 14 19:13:20.109: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:20.109: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:20.109: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:20.109: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
Nov 14 19:13:20.109: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:20.109: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:20.109: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:20.109: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:20.109: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:20.109: INFO:
Nov 14 19:13:21.998: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:21.998: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:21.998: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:21.998: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
Nov 14 19:13:21.998: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:21.998: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:21.998: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:21.998: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:21.998: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:21.998: INFO:
Nov 14 19:13:23.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:23.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:23.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:23.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
Nov 14 19:13:23.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:23.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:23.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:23.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:23.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:23.999: INFO:
Nov 14 19:13:25.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:25.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:25.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:25.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
Nov 14 19:13:25.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:25.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:25.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:25.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:25.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:25.993: INFO:
Nov 14 19:13:27.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:27.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:27.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:27.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
Nov 14 19:13:27.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:27.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:27.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:27.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:27.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:27.994: INFO:
Nov 14 19:13:30.001: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:30.001: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:30.001: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:30.001: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
Nov 14 19:13:30.001: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:30.001: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:30.001: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:30.001: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:30.001: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:30.001: INFO:
Nov 14 19:13:31.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:31.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:31.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:31.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
Nov 14 19:13:31.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:31.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:31.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:31.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:31.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:31.995: INFO:
Nov 14 19:13:33.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:33.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:33.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:33.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
Nov 14 19:13:33.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:33.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:33.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:33.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:33.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:33.994: INFO:
Nov 14 19:13:35.992: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:35.992: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:35.992: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:35.992: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
Nov 14 19:13:35.992: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:35.992: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:35.992: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:35.992: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:35.992: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:35.992: INFO:
Nov 14 19:13:37.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:37.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:37.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:37.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
Nov 14 19:13:37.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:37.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:37.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:37.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:37.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:37.994: INFO:
Nov 14 19:13:39.997: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:39.997: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:39.997: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:39.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
Nov 14 19:13:39.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:39.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:39.997: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:39.997: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:39.997: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:39.997: INFO:
Nov 14 19:13:41.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:41.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:41.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:41.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
Nov 14 19:13:41.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:41.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:41.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:41.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:41.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:41.994: INFO:
Nov 14 19:13:43.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:43.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:43.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:43.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
Nov 14 19:13:43.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:43.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:43.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:43.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:43.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:43.995: INFO:
Nov 14 19:13:45.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:45.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:45.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:45.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
Nov 14 19:13:45.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:45.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:45.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:45.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:45.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:45.994: INFO:
Nov 14 19:13:47.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:47.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:47.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:47.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
Nov 14 19:13:47.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:47.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:47.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:47.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:47.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:47.994: INFO:
Nov 14 19:13:49.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:49.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:49.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:49.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
Nov 14 19:13:49.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:49.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:49.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:49.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:49.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:49.995: INFO:
Nov 14 19:13:51.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:51.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:51.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:51.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
Nov 14 19:13:51.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:51.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:51.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:51.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:51.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:51.995: INFO:
Nov 14 19:13:53.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:53.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:53.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:53.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
Nov 14 19:13:53.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:53.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:53.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:53.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:53.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:53.999: INFO:
Nov 14 19:13:55.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:55.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:55.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:55.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
Nov 14 19:13:55.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:55.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:55.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:55.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:55.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:55.993: INFO:
Nov 14 19:13:57.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:57.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:57.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:57.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
Nov 14 19:13:57.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:57.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:57.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:57.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:57.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:57.995: INFO:
Nov 14 19:13:59.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:59.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:59.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:13:59.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
Nov 14 19:13:59.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:13:59.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:13:59.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:59.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:59.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:13:59.993: INFO:
Nov 14 19:14:02.000: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:02.000: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:02.000: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:02.000: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
Nov 14 19:14:02.000: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:02.000: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:02.000: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:02.000: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:02.000: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:02.000: INFO:
Nov 14 19:14:03.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:03.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:03.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:03.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
Nov 14 19:14:03.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:03.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:03.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:03.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:03.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:03.994: INFO:
Nov 14 19:14:05.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:05.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:05.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:05.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
Nov 14 19:14:05.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:05.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:05.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:05.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:05.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:05.994: INFO:
Nov 14 19:14:07.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:07.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:07.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:07.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
Nov 14 19:14:07.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:07.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:07.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:07.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:07.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:07.993: INFO:
Nov 14 19:14:09.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:09.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:09.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:09.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
Nov 14 19:14:09.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:09.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:09.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:09.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:09.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:09.994: INFO:
Nov 14 19:14:12.000: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:12.000: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:12.000: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:12.000: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
Nov 14 19:14:12.000: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:12.000: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:12.000: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:12.000: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:12.000: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:12.000: INFO:
Nov 14 19:14:13.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:13.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:13.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:13.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
Nov 14 19:14:13.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:13.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:13.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:13.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:13.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:13.993: INFO:
Nov 14 19:14:15.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:15.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:15.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:15.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
Nov 14 19:14:15.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:15.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:15.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:15.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:15.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:15.994: INFO:
Nov 14 19:14:17.992: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:17.992: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:17.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:17.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
Nov 14 19:14:17.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:17.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:17.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:17.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:17.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:17.993: INFO:
Nov 14 19:14:19.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:19.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:19.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:19.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
Nov 14 19:14:19.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:19.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:19.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:19.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:19.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:19.994: INFO:
Nov 14 19:14:21.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:21.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:21.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:21.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
Nov 14 19:14:21.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:21.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:21.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:21.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:21.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:21.994: INFO:
Nov 14 19:14:23.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:23.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:23.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:23.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
Nov 14 19:14:23.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:23.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:23.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:23.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:23.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:23.994: INFO:
Nov 14 19:14:25.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:25.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:25.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:25.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
Nov 14 19:14:25.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:25.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:25.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:25.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:25.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:25.994: INFO:
Nov 14 19:14:27.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:27.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:27.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:27.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
Nov 14 19:14:27.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:27.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:27.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:27.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:27.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:27.994: INFO:
Nov 14 19:14:29.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:29.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:29.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:29.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
Nov 14 19:14:29.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:29.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:29.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:29.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:29.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:29.995: INFO:
Nov 14 19:14:32.003: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:32.003: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:32.003: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:32.003: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
Nov 14 19:14:32.003: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:32.003: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:32.003: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:32.003: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:32.003: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:32.003: INFO:
Nov 14 19:14:33.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:33.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:33.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:33.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
Nov 14 19:14:33.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:33.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:33.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:33.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:33.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:33.994: INFO:
Nov 14 19:14:35.997: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:35.997: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:35.997: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:35.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
Nov 14 19:14:35.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:35.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:35.997: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:35.997: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:35.997: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:35.997: INFO:
Nov 14 19:14:38.000: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:38.000: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:38.000: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:38.000: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
Nov 14 19:14:38.000: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:38.000: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:38.000: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:38.000: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:38.000: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:38.000: INFO:
Nov 14 19:14:39.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:39.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:39.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:39.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
Nov 14 19:14:39.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:39.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:39.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:39.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:39.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:39.993: INFO:
Nov 14 19:14:41.996: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:41.996: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:41.996: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:41.996: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
Nov 14 19:14:41.996: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:41.996: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:41.996: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:41.996: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:41.996: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:41.997: INFO:
Nov 14 19:14:43.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:43.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:43.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:43.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
Nov 14 19:14:43.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:43.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:43.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:43.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:43.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:43.994: INFO:
Nov 14 19:14:45.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:45.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:45.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:45.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
Nov 14 19:14:45.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:45.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:45.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:45.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:45.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:45.993: INFO:
Nov 14 19:14:47.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:47.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:47.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:47.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
Nov 14 19:14:47.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:47.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:47.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:47.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:47.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:47.993: INFO:
Nov 14 19:14:49.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:49.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:49.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:49.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
Nov 14 19:14:49.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:49.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:49.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:49.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:49.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:49.995: INFO:
Nov 14 19:14:51.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:51.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:51.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:51.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
Nov 14 19:14:51.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:51.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:51.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:51.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:51.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:51.994: INFO:
Nov 14 19:14:53.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:53.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:53.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:53.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
Nov 14 19:14:53.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:53.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:53.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:53.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:53.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:53.993: INFO:
Nov 14 19:14:56.105: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:56.105: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:56.105: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:56.105: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
Nov 14 19:14:56.105: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:56.105: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:56.105: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:56.105: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:56.105: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:56.105: INFO:
Nov 14 19:14:57.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:57.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:57.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:57.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
Nov 14 19:14:57.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:57.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:57.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:57.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:57.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:57.995: INFO:
Nov 14 19:14:59.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:59.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:59.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:14:59.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
Nov 14 19:14:59.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:14:59.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:14:59.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:59.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:59.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:14:59.993: INFO:
Nov 14 19:15:01.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:01.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:01.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:01.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
Nov 14 19:15:01.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:01.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:01.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:01.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:01.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:01.995: INFO:
Nov 14 19:15:03.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:03.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:03.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:03.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
Nov 14 19:15:03.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:03.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:03.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:03.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:03.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:03.999: INFO:
Nov 14 19:15:05.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:05.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:05.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:05.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
Nov 14 19:15:05.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:05.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:05.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:05.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:05.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:05.993: INFO:
Nov 14 19:15:07.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:07.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:07.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:07.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
Nov 14 19:15:07.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:07.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:07.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:07.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:07.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:07.993: INFO:
Nov 14 19:15:09.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:09.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:09.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:09.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
Nov 14 19:15:09.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:09.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:09.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:09.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:09.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:09.994: INFO:
Nov 14 19:15:11.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:11.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:11.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:11.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
Nov 14 19:15:11.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:11.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:11.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:11.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:11.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:11.994: INFO:
Nov 14 19:15:13.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:13.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:13.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:13.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
Nov 14 19:15:13.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:13.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:13.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:13.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:13.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:13.995: INFO:
Nov 14 19:15:16.000: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:16.000: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:16.000: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:16.000: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
Nov 14 19:15:16.000: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:16.000: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:16.000: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:16.000: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:16.000: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:16.000: INFO:
Nov 14 19:15:17.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:17.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:17.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:17.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
Nov 14 19:15:17.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:17.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:17.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:17.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:17.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:17.995: INFO:
Nov 14 19:15:19.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:19.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:19.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:19.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
Nov 14 19:15:19.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:19.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:19.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:19.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:19.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:19.995: INFO:
Nov 14 19:15:22.012: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:22.012: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:22.012: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:22.012: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
Nov 14 19:15:22.012: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:22.012: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:22.012: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:22.012: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:22.012: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:22.012: INFO:
Nov 14 19:15:23.996: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:23.996: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:23.996: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:23.996: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
Nov 14 19:15:23.996: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:23.996: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:23.996: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:23.996: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:23.996: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:23.996: INFO:
Nov 14 19:15:25.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:25.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:25.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:25.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
Nov 14 19:15:25.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:25.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:25.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:25.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:25.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:25.995: INFO:
Nov 14 19:15:27.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:27.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:27.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:27.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
Nov 14 19:15:27.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:27.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:27.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:27.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:27.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:27.994: INFO:
Nov 14 19:15:29.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:29.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:29.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:29.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
Nov 14 19:15:29.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:29.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:29.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:29.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:29.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:29.995: INFO:
Nov 14 19:15:31.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:31.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:31.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:31.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
Nov 14 19:15:31.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:31.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:31.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:31.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:31.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:31.994: INFO:
Nov 14 19:15:33.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:33.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:33.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:33.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
Nov 14 19:15:33.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:33.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:33.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:33.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:33.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:33.994: INFO:
Nov 14 19:15:35.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:35.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:35.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:35.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
Nov 14 19:15:35.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:35.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:35.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:35.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:35.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:35.995: INFO:
Nov 14 19:15:37.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:37.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:37.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:37.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
Nov 14 19:15:37.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:37.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:37.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:37.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:37.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:37.994: INFO:
Nov 14 19:15:39.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:39.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:39.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:39.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
Nov 14 19:15:39.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:39.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:39.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:39.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:39.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:39.993: INFO:
Nov 14 19:15:41.996: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:41.996: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:41.996: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:41.996: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
Nov 14 19:15:41.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:41.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:41.997: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:41.997: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:41.997: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:41.997: INFO:
Nov 14 19:15:43.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:43.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:43.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:43.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
Nov 14 19:15:43.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:43.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:43.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:43.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:43.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:43.994: INFO:
Nov 14 19:15:45.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:45.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:45.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:45.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
Nov 14 19:15:45.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:45.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:45.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:45.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:45.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:45.993: INFO:
Nov 14 19:15:47.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:47.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:47.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:47.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
Nov 14 19:15:47.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:47.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:47.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:47.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:47.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:47.993: INFO:
Nov 14 19:15:49.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:49.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:49.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:49.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
Nov 14 19:15:49.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:49.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:49.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:49.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:49.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:49.993: INFO:
Nov 14 19:15:51.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:51.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:51.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:51.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
Nov 14 19:15:51.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:51.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:51.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:51.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:51.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:51.994: INFO:
Nov 14 19:15:53.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:53.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:53.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:53.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
Nov 14 19:15:53.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:53.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:53.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:53.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:53.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:53.994: INFO:
Nov 14 19:15:55.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:55.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:55.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:55.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
Nov 14 19:15:55.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:55.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:55.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:55.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:55.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:55.999: INFO:
Nov 14 19:15:57.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:57.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:57.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:57.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
Nov 14 19:15:57.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:57.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:57.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:57.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:57.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:57.994: INFO:
Nov 14 19:15:59.997: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:59.997: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:59.997: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:15:59.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
Nov 14 19:15:59.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:15:59.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:15:59.997: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:59.997: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:59.997: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:15:59.997: INFO:
Nov 14 19:16:01.997: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:01.997: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:01.997: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:01.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
Nov 14 19:16:01.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:01.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:01.997: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:01.997: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:01.997: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:01.997: INFO:
Nov 14 19:16:03.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:03.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:03.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:03.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
Nov 14 19:16:03.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:03.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:03.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:03.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:03.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:03.993: INFO:
Nov 14 19:16:05.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:05.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:05.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:05.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
Nov 14 19:16:05.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:05.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:05.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:05.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:05.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:05.993: INFO:
Nov 14 19:16:07.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:07.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:07.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:07.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
Nov 14 19:16:07.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:07.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:07.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:07.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:07.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:07.994: INFO:
Nov 14 19:16:09.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:09.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:09.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:09.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
Nov 14 19:16:09.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:09.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:09.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:09.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:09.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:09.993: INFO:
Nov 14 19:16:11.998: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:11.998: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:11.998: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:11.998: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
Nov 14 19:16:11.998: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:11.998: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:11.998: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:11.998: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:11.998: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:11.998: INFO:
Nov 14 19:16:13.996: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:13.996: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:13.996: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:13.996: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
Nov 14 19:16:13.996: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:13.996: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:13.996: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:13.996: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:13.996: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:13.996: INFO:
Nov 14 19:16:15.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:15.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:15.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:15.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
Nov 14 19:16:15.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:15.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:15.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:15.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:15.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:15.993: INFO:
Nov 14 19:16:17.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:17.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:17.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:17.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
Nov 14 19:16:17.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:17.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:17.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:17.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:17.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:17.994: INFO:
Nov 14 19:16:19.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:19.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:19.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:19.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
Nov 14 19:16:19.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:19.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:19.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:19.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:19.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:19.999: INFO:
Nov 14 19:16:21.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:21.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:21.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:21.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
Nov 14 19:16:21.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:21.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:21.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:21.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:21.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:21.993: INFO:
Nov 14 19:16:23.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:23.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:23.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:23.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
Nov 14 19:16:23.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:23.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:23.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:23.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:23.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:23.993: INFO:
Nov 14 19:16:25.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:25.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:25.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:25.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
Nov 14 19:16:25.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:25.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:25.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:25.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:25.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:25.993: INFO:
Nov 14 19:16:27.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:27.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:27.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:27.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
Nov 14 19:16:27.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:27.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:27.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:27.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:27.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:27.993: INFO:
Nov 14 19:16:29.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:29.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:29.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:29.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
Nov 14 19:16:29.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:29.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:29.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:29.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:29.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:29.994: INFO:
Nov 14 19:16:31.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:31.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:31.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:31.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
Nov 14 19:16:31.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:31.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:31.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:31.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:31.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:31.993: INFO:
Nov 14 19:16:33.992: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:33.992: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:33.992: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:33.992: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
Nov 14 19:16:33.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:33.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:33.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:33.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:33.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:33.993: INFO:
Nov 14 19:16:35.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:35.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:35.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:35.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
Nov 14 19:16:35.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:35.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:35.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:35.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:35.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:35.995: INFO:
Nov 14 19:16:37.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:37.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:37.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:37.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
Nov 14 19:16:37.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:37.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:37.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:37.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:37.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:37.993: INFO:
Nov 14 19:16:39.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:39.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:39.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:39.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
Nov 14 19:16:39.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:39.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:39.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:39.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:39.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:39.993: INFO:
Nov 14 19:16:41.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:41.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:41.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:41.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
Nov 14 19:16:41.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:41.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:41.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:41.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:41.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:41.995: INFO:
Nov 14 19:16:43.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:43.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:43.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:43.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
Nov 14 19:16:43.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:43.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:43.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:43.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:43.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:43.994: INFO:
Nov 14 19:16:46.006: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:46.006: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:46.006: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:46.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
Nov 14 19:16:46.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:46.006: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:46.006: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:46.006: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:46.006: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:46.006: INFO:
Nov 14 19:16:47.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:47.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:47.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:47.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
Nov 14 19:16:47.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:47.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:47.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:47.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:47.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:47.993: INFO:
Nov 14 19:16:49.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:49.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:49.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:49.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
Nov 14 19:16:49.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:49.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:49.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:49.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:49.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:49.993: INFO:
Nov 14 19:16:51.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:51.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:51.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:51.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
Nov 14 19:16:51.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:51.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:51.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:51.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:51.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:51.993: INFO:
Nov 14 19:16:53.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:53.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:53.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:53.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
Nov 14 19:16:53.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:53.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:53.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:53.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:53.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:53.993: INFO:
Nov 14 19:16:55.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:55.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:55.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:55.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
Nov 14 19:16:55.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:55.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:55.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:55.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:55.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:55.994: INFO:
Nov 14 19:16:57.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:57.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:57.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:57.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
Nov 14 19:16:57.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:57.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:57.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:57.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:57.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:57.994: INFO:
Nov 14 19:16:59.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:59.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:59.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:16:59.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
Nov 14 19:16:59.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:16:59.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:16:59.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:59.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:59.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:16:59.993: INFO:
Nov 14 19:17:01.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:01.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:01.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:01.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
Nov 14 19:17:01.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:01.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:01.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:01.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:01.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:01.993: INFO:
Nov 14 19:17:03.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:03.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:03.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:03.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
Nov 14 19:17:03.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:03.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:03.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:03.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:03.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:03.993: INFO:
Nov 14 19:17:05.996: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:05.996: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:05.996: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:05.996: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
Nov 14 19:17:05.996: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:05.996: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:05.996: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:05.996: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:05.996: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:05.996: INFO:
Nov 14 19:17:07.996: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:07.996: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:07.996: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:07.996: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
Nov 14 19:17:07.996: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:07.996: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:07.996: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:07.996: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:07.996: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:07.996: INFO:
Nov 14 19:17:09.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:09.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:09.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:09.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
Nov 14 19:17:09.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:09.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:09.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:09.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:09.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:09.994: INFO:
Nov 14 19:17:11.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:11.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:11.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:11.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
Nov 14 19:17:11.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:11.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:11.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:11.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:11.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:11.995: INFO:
Nov 14 19:17:13.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:13.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:13.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:13.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
Nov 14 19:17:13.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:13.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:13.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:13.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:13.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:13.993: INFO:
Nov 14 19:17:15.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:15.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:15.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:15.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
Nov 14 19:17:15.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:15.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:15.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:15.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:15.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:15.994: INFO:
Nov 14 19:17:17.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:17.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:17.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:17.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
Nov 14 19:17:17.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:17.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:17.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:17.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:17.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:17.993: INFO:
Nov 14 19:17:19.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:19.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:19.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:19.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
Nov 14 19:17:19.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:19.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:19.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:19.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:19.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:19.995: INFO:
Nov 14 19:17:21.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:21.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:21.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:21.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
Nov 14 19:17:21.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:21.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:21.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:21.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:21.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:21.993: INFO:
Nov 14 19:17:24.104: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:24.104: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:24.104: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:24.104: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
Nov 14 19:17:24.104: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:24.104: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:24.104: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:24.104: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:24.104: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:24.104: INFO:
Nov 14 19:17:25.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:25.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:25.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:25.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
Nov 14 19:17:25.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:25.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:25.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:25.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:25.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:25.993: INFO:
Nov 14 19:17:28.019: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:28.019: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:28.019: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:28.019: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
Nov 14 19:17:28.019: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:28.019: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:28.019: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:28.019: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:28.019: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:28.019: INFO:
Nov 14 19:17:30.006: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:30.006: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:30.006: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:30.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
Nov 14 19:17:30.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:30.006: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:30.006: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:30.006: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:30.006: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:30.006: INFO:
Nov 14 19:17:32.006: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:32.006: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:32.006: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:32.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
Nov 14 19:17:32.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:32.006: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:32.006: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:32.006: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:32.006: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:32.006: INFO:
Nov 14 19:17:34.006: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:34.006: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:34.006: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:34.006: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
Nov 14 19:17:34.006: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:34.006: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:34.006: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:34.006: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:34.006: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:34.006: INFO:
Nov 14 19:17:36.007: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:36.007: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:36.007: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:36.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
Nov 14 19:17:36.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:36.007: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:36.007: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:36.007: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:36.007: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:36.007: INFO:
Nov 14 19:17:38.010: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:38.010: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:38.010: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:38.010: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
Nov 14 19:17:38.010: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:38.010: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:38.010: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:38.010: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:38.010: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:38.010: INFO:
Nov 14 19:17:40.007: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:40.007: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:40.007: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:40.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
Nov 14 19:17:40.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:40.007: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:40.007: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:40.007: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:40.007: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:40.007: INFO:
Nov 14 19:17:41.992: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:41.992: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:41.992: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:41.992: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
Nov 14 19:17:41.992: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:41.992: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:41.992: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:41.992: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:41.992: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:41.992: INFO:
Nov 14 19:17:43.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:43.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:43.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:43.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
Nov 14 19:17:43.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:43.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:43.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:43.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:43.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:43.994: INFO:
Nov 14 19:17:45.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:45.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:45.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:45.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
Nov 14 19:17:45.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:45.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:45.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:45.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:45.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:45.993: INFO:
Nov 14 19:17:47.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:47.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:47.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:47.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
Nov 14 19:17:47.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:47.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:47.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:47.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:47.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:47.995: INFO:
Nov 14 19:17:49.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:49.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:49.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:49.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
Nov 14 19:17:49.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:49.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:49.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:49.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:49.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:49.994: INFO:
Nov 14 19:17:51.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:51.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:51.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:51.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
Nov 14 19:17:51.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:51.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:51.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:51.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:51.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:51.994: INFO:
Nov 14 19:17:53.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:53.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:53.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:53.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
Nov 14 19:17:53.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:53.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:53.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:53.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:53.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:53.993: INFO:
Nov 14 19:17:55.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:55.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:55.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:55.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
Nov 14 19:17:55.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:55.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:55.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:55.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:55.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:55.993: INFO:
Nov 14 19:17:57.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:57.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:57.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:57.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
Nov 14 19:17:57.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:57.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:57.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:57.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:57.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:57.995: INFO:
Nov 14 19:17:59.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:59.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:59.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:17:59.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
Nov 14 19:17:59.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:17:59.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:17:59.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:59.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:59.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:17:59.994: INFO:
Nov 14 19:18:02.001: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:02.001: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:02.001: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:02.001: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
Nov 14 19:18:02.001: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:02.001: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:02.001: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:02.001: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:02.001: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:02.001: INFO:
Nov 14 19:18:03.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:03.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:03.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:03.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
Nov 14 19:18:03.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:03.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:03.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:03.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:03.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:03.994: INFO:
Nov 14 19:18:05.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:05.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:05.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:05.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
Nov 14 19:18:05.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:05.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:05.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:05.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:05.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:05.994: INFO:
Nov 14 19:18:07.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:07.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:07.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:07.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
Nov 14 19:18:07.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:07.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:07.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:07.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:07.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:07.994: INFO:
Nov 14 19:18:09.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:09.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:09.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:09.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
Nov 14 19:18:09.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:09.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:09.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:09.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:09.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:09.994: INFO:
Nov 14 19:18:11.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:11.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:11.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:11.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
Nov 14 19:18:11.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:11.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:11.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:11.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:11.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:11.995: INFO:
Nov 14 19:18:13.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:13.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:13.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:13.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
Nov 14 19:18:13.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:13.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:13.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:13.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:13.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:13.993: INFO:
Nov 14 19:18:15.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:15.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:15.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:15.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
Nov 14 19:18:15.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:15.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:15.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:15.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:15.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:15.993: INFO:
Nov 14 19:18:17.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:17.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:17.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:17.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
Nov 14 19:18:17.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:17.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:17.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:17.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:17.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:17.995: INFO:
Nov 14 19:18:19.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:19.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:19.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:19.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
Nov 14 19:18:19.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:19.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:19.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:19.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:19.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:19.994: INFO:
Nov 14 19:18:21.998: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:21.998: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:21.998: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:21.998: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
Nov 14 19:18:21.998: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:21.998: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:21.998: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:21.998: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:21.998: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:21.998: INFO:
Nov 14 19:18:23.992: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:23.992: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:23.992: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:23.992: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
Nov 14 19:18:23.992: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:23.992: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:23.992: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:23.992: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:23.992: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:23.992: INFO:
Nov 14 19:18:25.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:25.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:25.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:25.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
Nov 14 19:18:25.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:25.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:25.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:25.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:25.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:25.993: INFO:
Nov 14 19:18:27.996: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:27.996: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:27.996: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:27.996: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
Nov 14 19:18:27.996: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:27.996: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:27.996: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:27.996: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:27.996: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:27.996: INFO:
Nov 14 19:18:29.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:29.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:29.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:29.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
Nov 14 19:18:29.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:29.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:29.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:29.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:29.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:29.995: INFO:
Nov 14 19:18:31.996: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:31.996: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:31.996: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:31.996: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
Nov 14 19:18:31.996: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:31.996: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:31.996: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:31.996: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:31.996: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:31.996: INFO:
Nov 14 19:18:33.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:33.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:33.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:33.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
Nov 14 19:18:33.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:33.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:33.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:33.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:33.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:33.994: INFO:
Nov 14 19:18:35.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:35.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:35.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:35.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
Nov 14 19:18:35.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:35.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:35.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:35.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:35.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:35.994: INFO:
Nov 14 19:18:37.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:37.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:37.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:37.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
Nov 14 19:18:37.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:37.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:37.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:37.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:37.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:37.994: INFO:
Nov 14 19:18:39.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:39.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:39.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:39.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
Nov 14 19:18:39.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:39.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:39.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:39.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:39.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:39.993: INFO:
Nov 14 19:18:41.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:41.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:41.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:41.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
Nov 14 19:18:41.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:41.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:41.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:41.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:41.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:41.993: INFO:
Nov 14 19:18:43.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:43.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:43.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:43.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
Nov 14 19:18:43.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:43.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:43.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:43.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:43.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:43.994: INFO:
Nov 14 19:18:45.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:45.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:45.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:45.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
Nov 14 19:18:45.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:45.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:45.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:45.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:45.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:45.993: INFO:
Nov 14 19:18:47.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:47.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:47.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:47.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
Nov 14 19:18:47.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:47.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:47.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:47.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:47.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:47.993: INFO:
Nov 14 19:18:49.997: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:49.997: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:49.997: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:49.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
Nov 14 19:18:49.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:49.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:49.997: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:49.997: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:49.997: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:49.997: INFO:
Nov 14 19:18:51.996: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:51.996: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:51.996: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:51.996: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
Nov 14 19:18:51.996: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:51.996: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:51.996: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:51.996: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:51.996: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:51.996: INFO:
Nov 14 19:18:53.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:53.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:53.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:53.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
Nov 14 19:18:53.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:53.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:53.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:53.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:53.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:53.994: INFO:
Nov 14 19:18:55.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:55.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:55.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:55.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
Nov 14 19:18:55.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:55.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:55.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:55.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:55.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:55.995: INFO:
Nov 14 19:18:57.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:57.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:57.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:57.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
Nov 14 19:18:57.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:57.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:57.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:57.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:57.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:57.994: INFO:
Nov 14 19:18:59.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:59.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:59.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:18:59.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
Nov 14 19:18:59.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:18:59.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:18:59.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:59.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:59.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:18:59.993: INFO:
Nov 14 19:19:01.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:01.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:01.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:01.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
Nov 14 19:19:01.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:01.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:01.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:01.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:01.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:01.994: INFO:
Nov 14 19:19:03.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:03.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:03.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:03.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
Nov 14 19:19:03.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:03.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:03.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:03.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:03.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:03.994: INFO:
Nov 14 19:19:05.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:05.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:05.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:05.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
Nov 14 19:19:05.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:05.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:05.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:05.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:05.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:05.993: INFO:
Nov 14 19:19:07.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:07.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:07.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:07.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
Nov 14 19:19:07.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:07.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:07.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:07.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:07.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:07.993: INFO:
Nov 14 19:19:09.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:09.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:09.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:09.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
Nov 14 19:19:09.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:09.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:09.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:09.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:09.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:09.993: INFO:
Nov 14 19:19:11.997: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:11.997: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:11.997: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:11.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
Nov 14 19:19:11.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:11.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:11.997: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:11.997: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:11.997: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:11.997: INFO:
Nov 14 19:19:13.996: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:13.996: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:13.996: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:13.996: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
Nov 14 19:19:13.996: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:13.996: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:13.996: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:13.996: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:13.996: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:13.996: INFO:
Nov 14 19:19:15.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:15.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:15.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:15.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
Nov 14 19:19:15.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:15.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:15.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:15.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:15.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:15.995: INFO:
Nov 14 19:19:17.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:17.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:17.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:17.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
Nov 14 19:19:17.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:17.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:17.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:17.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:17.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:17.995: INFO:
Nov 14 19:19:20.000: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:20.000: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:20.000: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:20.000: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
Nov 14 19:19:20.000: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:20.000: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:20.000: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:20.000: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:20.000: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:20.000: INFO:
Nov 14 19:19:21.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:21.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:21.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:21.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
Nov 14 19:19:21.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:21.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:21.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:21.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:21.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:21.994: INFO:
Nov 14 19:19:23.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:23.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:23.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:23.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
Nov 14 19:19:23.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:23.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:23.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:23.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:23.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:23.995: INFO:
Nov 14 19:19:25.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:25.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:25.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:25.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
Nov 14 19:19:25.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:25.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:25.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:25.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:25.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:25.993: INFO:
Nov 14 19:19:27.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:27.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:27.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:27.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
Nov 14 19:19:27.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:27.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:27.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:27.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:27.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:27.995: INFO:
Nov 14 19:19:29.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:29.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:29.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:29.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
Nov 14 19:19:29.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:29.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:29.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:29.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:29.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:29.994: INFO:
Nov 14 19:19:31.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:31.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:31.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:31.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
Nov 14 19:19:31.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:31.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:31.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:31.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:31.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:31.993: INFO:
Nov 14 19:19:33.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:33.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:33.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:33.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
Nov 14 19:19:33.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:33.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:33.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:33.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:33.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:33.993: INFO:
Nov 14 19:19:35.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:35.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:35.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:35.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
Nov 14 19:19:35.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:35.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:35.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:35.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:35.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:35.994: INFO:
Nov 14 19:19:37.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:37.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:37.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:37.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
Nov 14 19:19:37.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:37.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:37.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:37.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:37.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:37.994: INFO:
Nov 14 19:19:39.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:39.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:39.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:39.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
Nov 14 19:19:39.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:39.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:39.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:39.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:39.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:39.993: INFO:
Nov 14 19:19:41.992: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:41.992: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:41.992: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:41.992: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
Nov 14 19:19:41.992: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:41.992: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:41.992: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:41.992: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:41.992: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:41.992: INFO:
Nov 14 19:19:43.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:43.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:43.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:43.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
Nov 14 19:19:43.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:43.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:43.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:43.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:43.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:43.994: INFO:
Nov 14 19:19:45.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:45.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:45.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:45.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
Nov 14 19:19:45.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:45.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:45.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:45.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:45.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:45.993: INFO:
Nov 14 19:19:47.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:47.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:47.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:47.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
Nov 14 19:19:47.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:47.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:47.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:47.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:47.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:47.994: INFO:
Nov 14 19:19:49.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:49.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:49.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:49.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
Nov 14 19:19:49.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:49.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:49.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:49.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:49.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:49.993: INFO:
Nov 14 19:19:51.996: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:51.996: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:51.996: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:51.996: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
Nov 14 19:19:51.996: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:51.996: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:51.996: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:51.996: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:51.996: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:51.996: INFO:
Nov 14 19:19:53.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:53.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:53.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:53.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
Nov 14 19:19:53.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:53.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:53.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:53.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:53.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:53.994: INFO:
Nov 14 19:19:55.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:55.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:55.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:55.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
Nov 14 19:19:55.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:55.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:55.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:55.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:55.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:55.995: INFO:
Nov 14 19:19:57.992: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:57.992: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:57.992: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:57.992: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
Nov 14 19:19:57.992: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:57.992: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:57.992: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:57.992: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:57.992: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:57.992: INFO:
Nov 14 19:19:59.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:59.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:59.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:19:59.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
Nov 14 19:19:59.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:19:59.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:19:59.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:59.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:59.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:19:59.993: INFO:
Nov 14 19:20:01.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:01.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:01.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:01.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
Nov 14 19:20:01.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:01.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:01.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:01.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:01.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:01.994: INFO:
Nov 14 19:20:03.997: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:03.997: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:03.997: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:03.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
Nov 14 19:20:03.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:03.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:03.997: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:03.997: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:03.997: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:03.997: INFO:
Nov 14 19:20:05.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:05.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:05.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:05.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
Nov 14 19:20:05.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:05.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:05.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:05.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:05.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:05.994: INFO:
Nov 14 19:20:07.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:07.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:07.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:07.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
Nov 14 19:20:07.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:07.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:07.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:07.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:07.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:07.995: INFO:
Nov 14 19:20:09.999: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:09.999: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:09.999: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:09.999: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
Nov 14 19:20:09.999: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:09.999: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:09.999: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:09.999: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:09.999: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:09.999: INFO:
Nov 14 19:20:11.997: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:11.997: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:11.997: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:11.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
Nov 14 19:20:11.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:11.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:11.997: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:11.997: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:11.997: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:11.997: INFO:
Nov 14 19:20:13.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:13.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:13.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:13.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
Nov 14 19:20:13.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:13.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:13.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:13.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:13.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:13.994: INFO:
Nov 14 19:20:15.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:15.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:15.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:15.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
Nov 14 19:20:15.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:15.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:15.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:15.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:15.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:15.994: INFO:
Nov 14 19:20:17.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:17.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:17.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:17.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
Nov 14 19:20:17.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:17.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:17.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:17.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:17.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:17.995: INFO:
Nov 14 19:20:19.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:19.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:19.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:19.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
Nov 14 19:20:19.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:19.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:19.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:19.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:19.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:19.994: INFO:
Nov 14 19:20:21.997: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:21.997: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:21.997: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:21.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
Nov 14 19:20:21.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:21.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:21.997: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:21.997: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:21.997: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:21.997: INFO:
Nov 14 19:20:23.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:23.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:23.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:23.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
Nov 14 19:20:23.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:23.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:23.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:23.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:23.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:23.993: INFO:
Nov 14 19:20:25.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:25.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:25.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:25.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
Nov 14 19:20:25.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:25.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:25.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:25.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:25.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:25.994: INFO:
Nov 14 19:20:27.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:27.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:27.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:27.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
Nov 14 19:20:27.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:27.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:27.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:27.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:27.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:27.993: INFO:
Nov 14 19:20:29.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:29.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:29.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:29.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
Nov 14 19:20:29.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:29.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:29.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:29.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:29.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:29.993: INFO:
Nov 14 19:20:31.998: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:31.998: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:31.998: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:31.998: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
Nov 14 19:20:31.998: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:31.998: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:31.998: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:31.998: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:31.998: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:31.998: INFO:
Nov 14 19:20:33.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:33.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:33.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:33.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
Nov 14 19:20:33.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:33.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:33.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:33.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:33.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:33.994: INFO:
Nov 14 19:20:36.002: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:36.002: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:36.002: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:36.002: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
Nov 14 19:20:36.002: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:36.002: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:36.002: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:36.002: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:36.002: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:36.002: INFO:
Nov 14 19:20:37.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:37.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:37.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:37.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
Nov 14 19:20:37.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:37.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:37.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:37.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:37.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:37.994: INFO:
Nov 14 19:20:39.996: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:39.996: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:39.996: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:39.996: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
Nov 14 19:20:39.996: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:39.996: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:39.996: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:39.996: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:39.996: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:39.996: INFO:
Nov 14 19:20:41.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:41.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:41.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:41.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
Nov 14 19:20:41.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:41.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:41.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:41.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:41.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:41.995: INFO:
Nov 14 19:20:43.992: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:43.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:43.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:43.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
Nov 14 19:20:43.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:43.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:43.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:43.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:43.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:43.993: INFO:
Nov 14 19:20:45.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:45.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:45.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:45.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
Nov 14 19:20:45.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:45.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:45.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:45.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:45.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:45.994: INFO:
Nov 14 19:20:47.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:47.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:47.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:47.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
Nov 14 19:20:47.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:47.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:47.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:47.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:47.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:47.995: INFO:
Nov 14 19:20:49.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:49.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:49.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:49.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
Nov 14 19:20:49.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:49.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:49.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:49.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:49.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:49.994: INFO:
Nov 14 19:20:52.106: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:52.106: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:52.106: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:52.106: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
Nov 14 19:20:52.106: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:52.106: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:52.106: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:52.106: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:52.106: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:52.106: INFO:
Nov 14 19:20:53.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:53.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:53.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:53.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
Nov 14 19:20:53.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:53.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:53.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:53.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:53.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:53.994: INFO:
Nov 14 19:20:55.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:55.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:55.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:55.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
Nov 14 19:20:55.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:55.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:55.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:55.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:55.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:55.994: INFO:
Nov 14 19:20:57.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:57.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:57.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:57.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
Nov 14 19:20:57.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:57.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:57.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:57.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:57.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:57.994: INFO:
Nov 14 19:20:59.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:59.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:59.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:20:59.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
Nov 14 19:20:59.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:20:59.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:20:59.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:59.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:59.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:20:59.994: INFO:
Nov 14 19:21:01.996: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:01.996: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:01.996: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:01.996: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
Nov 14 19:21:01.996: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:01.996: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:01.996: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:01.996: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:01.996: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:01.996: INFO:
Nov 14 19:21:03.997: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:03.997: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:03.997: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:03.997: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
Nov 14 19:21:03.997: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:03.997: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:03.997: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:03.997: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:03.997: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:03.997: INFO:
Nov 14 19:21:05.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:05.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:05.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:05.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
Nov 14 19:21:05.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:05.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:05.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:05.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:05.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:05.994: INFO:
Nov 14 19:21:07.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:07.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:07.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:07.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
Nov 14 19:21:07.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:07.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:07.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:07.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:07.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:07.994: INFO:
Nov 14 19:21:09.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:09.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:09.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:09.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
Nov 14 19:21:09.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:09.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:09.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:09.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:09.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:09.994: INFO:
Nov 14 19:21:11.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:11.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:11.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:11.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
Nov 14 19:21:11.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:11.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:11.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:11.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:11.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:11.994: INFO:
Nov 14 19:21:13.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:13.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:13.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:13.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
Nov 14 19:21:13.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:13.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:13.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:13.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:13.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:13.993: INFO:
Nov 14 19:21:15.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:15.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:15.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:15.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
Nov 14 19:21:15.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:15.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:15.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:15.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:15.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:15.995: INFO:
Nov 14 19:21:17.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:17.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:17.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:17.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
Nov 14 19:21:17.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:17.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:17.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:17.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:17.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:17.993: INFO:
Nov 14 19:21:19.996: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:19.996: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:19.996: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:19.996: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
Nov 14 19:21:19.996: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:19.996: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:19.996: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:19.996: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:19.996: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:19.996: INFO:
Nov 14 19:21:21.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:21.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:21.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:21.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
Nov 14 19:21:21.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:21.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:21.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:21.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:21.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:21.994: INFO:
Nov 14 19:21:23.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:23.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:23.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:23.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
Nov 14 19:21:23.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:23.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:23.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:23.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:23.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:23.993: INFO:
Nov 14 19:21:25.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:25.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:25.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:25.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
Nov 14 19:21:25.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:25.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:25.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:25.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:25.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:25.994: INFO:
Nov 14 19:21:27.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:27.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:27.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:27.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
Nov 14 19:21:27.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:27.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:27.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:27.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:27.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:27.993: INFO:
Nov 14 19:21:29.998: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:29.998: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:29.998: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:29.998: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
Nov 14 19:21:29.998: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:29.998: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:29.998: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:29.998: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:29.998: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:29.998: INFO:
Nov 14 19:21:31.995: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:31.995: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:31.995: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:31.995: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
Nov 14 19:21:31.995: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:31.995: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:31.995: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:31.995: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:31.995: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:31.995: INFO:
Nov 14 19:21:33.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:33.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:33.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:33.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
Nov 14 19:21:33.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:33.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:33.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:33.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:33.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:33.994: INFO:
Nov 14 19:21:35.994: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:35.994: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:35.994: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:35.994: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Nov 14 19:21:35.994: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:35.994: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:35.994: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:35.994: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:35.994: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:35.994: INFO:
Nov 14 19:21:37.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:37.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:37.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:37.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Nov 14 19:21:37.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:37.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:37.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:37.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:37.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:37.993: INFO:
Nov 14 19:21:39.993: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:39.993: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:39.993: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:39.993: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 14 19:21:39.993: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:39.993: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:39.993: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:39.993: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:39.993: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:39.993: INFO:
Nov 14 19:21:40.117: INFO: The status of Pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:40.117: INFO: The status of Pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:40.117: INFO: The status of Pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 14 19:21:40.117: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 14 19:21:40.117: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 14 19:21:40.117: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:40.117: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:40.117: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:40.117: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:40.117: INFO:
�[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m11/14/22 19:21:40.117�[0m
�[1mSTEP:�[0m Found 126 events. �[38;5;243m11/14/22 19:21:40.166�[0m
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:14 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-185r3j-control-plane-r6sjn_8ac0e67e-35ee-4ff3-81bc-f83fe090f49a became leader
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:14 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-185r3j-control-plane-r6sjn_116ffe76-ab50-4233-b915-846d12c698b3 became leader
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:19 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-787d4945fb to 2
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:19 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-28shf
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:19 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-g55nf
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:19 +0000 UTC - event for coredns-787d4945fb-28shf: {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 19:21:40.166: INFO: At 2022-11-14 19:07:19 +0000 UTC - event for coredns-787d4945fb-g55nf: {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 19:21:40.166: INFO: At 2022-11-14 19:07:19 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-2cjlb
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:19 +0000 UTC - event for kube-proxy-2cjlb: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-2cjlb to capz-conf-185r3j-control-plane-r6sjn
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:20 +0000 UTC - event for kube-proxy-2cjlb: {kubelet capz-conf-185r3j-control-plane-r6sjn} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.85_0050669549cb7e"
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:22 +0000 UTC - event for kube-proxy-2cjlb: {kubelet capz-conf-185r3j-control-plane-r6sjn} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.85_0050669549cb7e" in 2.302515095s (2.302519896s including waiting)
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:22 +0000 UTC - event for kube-proxy-2cjlb: {kubelet capz-conf-185r3j-control-plane-r6sjn} Created: Created container kube-proxy
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:22 +0000 UTC - event for kube-proxy-2cjlb: {kubelet capz-conf-185r3j-control-plane-r6sjn} Started: Started container kube-proxy
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:45 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:45 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-26vvh
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:45 +0000 UTC - event for metrics-server-c9574f845-26vvh: {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 19:21:40.166: INFO: At 2022-11-14 19:07:47 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:47 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-jtbsh
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:47 +0000 UTC - event for calico-kube-controllers-657b584867-jtbsh: {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 19:21:40.166: INFO: At 2022-11-14 19:07:47 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-4h45g
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:47 +0000 UTC - event for calico-node-4h45g: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-4h45g to capz-conf-185r3j-control-plane-r6sjn
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:48 +0000 UTC - event for calico-node-4h45g: {kubelet capz-conf-185r3j-control-plane-r6sjn} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:54 +0000 UTC - event for calico-node-4h45g: {kubelet capz-conf-185r3j-control-plane-r6sjn} Created: Created container upgrade-ipam
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:54 +0000 UTC - event for calico-node-4h45g: {kubelet capz-conf-185r3j-control-plane-r6sjn} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 6.606038373s (6.606045373s including waiting)
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:55 +0000 UTC - event for calico-node-4h45g: {kubelet capz-conf-185r3j-control-plane-r6sjn} Started: Started container upgrade-ipam
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:58 +0000 UTC - event for calico-node-4h45g: {kubelet capz-conf-185r3j-control-plane-r6sjn} Created: Created container install-cni
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:58 +0000 UTC - event for calico-node-4h45g: {kubelet capz-conf-185r3j-control-plane-r6sjn} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:07:59 +0000 UTC - event for calico-node-4h45g: {kubelet capz-conf-185r3j-control-plane-r6sjn} Started: Started container install-cni
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:01 +0000 UTC - event for calico-kube-controllers-657b584867-jtbsh: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-jtbsh to capz-conf-185r3j-control-plane-r6sjn
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:01 +0000 UTC - event for calico-node-4h45g: {kubelet capz-conf-185r3j-control-plane-r6sjn} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:01 +0000 UTC - event for coredns-787d4945fb-28shf: {kubelet capz-conf-185r3j-control-plane-r6sjn} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "4822a732fff30235c6733bad3f592bf41307fae7a883e753cec96f715e0ed0a5": 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 19:21:40.166: INFO: At 2022-11-14 19:08:01 +0000 UTC - event for coredns-787d4945fb-28shf: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-28shf to capz-conf-185r3j-control-plane-r6sjn
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:01 +0000 UTC - event for coredns-787d4945fb-g55nf: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-g55nf to capz-conf-185r3j-control-plane-r6sjn
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:01 +0000 UTC - event for coredns-787d4945fb-g55nf: {kubelet capz-conf-185r3j-control-plane-r6sjn} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "9629d089567d2740c8df8e594eefb4c14fc93ca6c7cbc26876fdfd8a8e2a5969": 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 19:21:40.166: INFO: At 2022-11-14 19:08:01 +0000 UTC - event for metrics-server-c9574f845-26vvh: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-26vvh to capz-conf-185r3j-control-plane-r6sjn
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:02 +0000 UTC - event for calico-kube-controllers-657b584867-jtbsh: {kubelet capz-conf-185r3j-control-plane-r6sjn} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "513ff75f7529023859039236efa0749c86d6d36898cfbe4fac5fc194ff8040ff": 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 19:21:40.166: INFO: At 2022-11-14 19:08:02 +0000 UTC - event for metrics-server-c9574f845-26vvh: {kubelet capz-conf-185r3j-control-plane-r6sjn} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "568d2cf3c7e2c345781eb915e7f21ae527a467372e5e0ff5a63a1c443c69fffb": 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 19:21:40.166: INFO: At 2022-11-14 19:08:09 +0000 UTC - event for calico-node-4h45g: {kubelet capz-conf-185r3j-control-plane-r6sjn} Started: Started container calico-node
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:09 +0000 UTC - event for calico-node-4h45g: {kubelet capz-conf-185r3j-control-plane-r6sjn} 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 19:21:40.166: INFO: At 2022-11-14 19:08:09 +0000 UTC - event for calico-node-4h45g: {kubelet capz-conf-185r3j-control-plane-r6sjn} Created: Created container calico-node
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:09 +0000 UTC - event for calico-node-4h45g: {kubelet capz-conf-185r3j-control-plane-r6sjn} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 7.365202155s (7.365207256s including waiting)
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:14 +0000 UTC - event for coredns-787d4945fb-28shf: {kubelet capz-conf-185r3j-control-plane-r6sjn} Started: Started container coredns
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:14 +0000 UTC - event for coredns-787d4945fb-28shf: {kubelet capz-conf-185r3j-control-plane-r6sjn} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:14 +0000 UTC - event for coredns-787d4945fb-28shf: {kubelet capz-conf-185r3j-control-plane-r6sjn} Created: Created container coredns
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:14 +0000 UTC - event for coredns-787d4945fb-28shf: {kubelet capz-conf-185r3j-control-plane-r6sjn} Unhealthy: Readiness probe failed: Get "http://192.168.204.193:8181/ready": dial tcp 192.168.204.193:8181: connect: connection refused
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:15 +0000 UTC - event for calico-kube-controllers-657b584867-jtbsh: {kubelet capz-conf-185r3j-control-plane-r6sjn} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0"
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:15 +0000 UTC - event for metrics-server-c9574f845-26vvh: {kubelet capz-conf-185r3j-control-plane-r6sjn} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:16 +0000 UTC - event for coredns-787d4945fb-g55nf: {kubelet capz-conf-185r3j-control-plane-r6sjn} Started: Started container coredns
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:16 +0000 UTC - event for coredns-787d4945fb-g55nf: {kubelet capz-conf-185r3j-control-plane-r6sjn} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:16 +0000 UTC - event for coredns-787d4945fb-g55nf: {kubelet capz-conf-185r3j-control-plane-r6sjn} Created: Created container coredns
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:16 +0000 UTC - event for coredns-787d4945fb-g55nf: {kubelet capz-conf-185r3j-control-plane-r6sjn} Unhealthy: Readiness probe failed: Get "http://192.168.204.196:8181/ready": dial tcp 192.168.204.196:8181: connect: connection refused
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:19 +0000 UTC - event for metrics-server-c9574f845-26vvh: {kubelet capz-conf-185r3j-control-plane-r6sjn} Created: Created container metrics-server
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:19 +0000 UTC - event for metrics-server-c9574f845-26vvh: {kubelet capz-conf-185r3j-control-plane-r6sjn} Started: Started container metrics-server
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:19 +0000 UTC - event for metrics-server-c9574f845-26vvh: {kubelet capz-conf-185r3j-control-plane-r6sjn} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 4.212337877s (4.212825784s including waiting)
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:21 +0000 UTC - event for coredns-787d4945fb-28shf: {kubelet capz-conf-185r3j-control-plane-r6sjn} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:21 +0000 UTC - event for coredns-787d4945fb-g55nf: {kubelet capz-conf-185r3j-control-plane-r6sjn} Unhealthy: Readiness probe failed: HTTP probe failed with statuscode: 503
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:25 +0000 UTC - event for calico-kube-controllers-657b584867-jtbsh: {kubelet capz-conf-185r3j-control-plane-r6sjn} Created: Created container calico-kube-controllers
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:25 +0000 UTC - event for calico-kube-controllers-657b584867-jtbsh: {kubelet capz-conf-185r3j-control-plane-r6sjn} Started: Started container calico-kube-controllers
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:08:25 +0000 UTC - event for calico-kube-controllers-657b584867-jtbsh: {kubelet capz-conf-185r3j-control-plane-r6sjn} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 5.818725321s (9.923645655s including waiting)
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:01 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-pfnw6
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:01 +0000 UTC - event for calico-node-windows-pfnw6: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-pfnw6 to capz-conf-krg8l
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:01 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-4mn65
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:01 +0000 UTC - event for containerd-logger-4mn65: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-4mn65 to capz-conf-krg8l
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:01 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-69qmt
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:01 +0000 UTC - event for kube-proxy-windows-69qmt: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-69qmt to capz-conf-krg8l
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:03 +0000 UTC - event for calico-node-windows-pfnw6: {kubelet capz-conf-krg8l} FailedMount: MountVolume.SetUp failed for volume "kubeadm-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:05 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-v2t6g
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:05 +0000 UTC - event for containerd-logger-v2t6g: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-v2t6g to capz-conf-d9m9m
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:05 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-8ntns
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:06 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-jbdps
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:06 +0000 UTC - event for calico-node-windows-jbdps: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-jbdps to capz-conf-d9m9m
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:06 +0000 UTC - event for kube-proxy-windows-8ntns: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-8ntns to capz-conf-d9m9m
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:08 +0000 UTC - event for calico-node-windows-jbdps: {kubelet capz-conf-d9m9m} FailedMount: MountVolume.SetUp failed for volume "calico-static-rules" : failed to sync configmap cache: timed out waiting for the condition
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:08 +0000 UTC - event for containerd-logger-v2t6g: {kubelet capz-conf-d9m9m} FailedMount: MountVolume.SetUp failed for volume "containerd-logger-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:17 +0000 UTC - event for calico-node-windows-pfnw6: {kubelet capz-conf-krg8l} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:17 +0000 UTC - event for containerd-logger-4mn65: {kubelet capz-conf-krg8l} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:17 +0000 UTC - event for kube-proxy-windows-69qmt: {kubelet capz-conf-krg8l} Pulled: Container image "sigwindowstools/kube-proxy:v1.26.0-beta.0.70_f5d6ffc86771e2-calico-hostprocess" already present on machine
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:17 +0000 UTC - event for kube-proxy-windows-69qmt: {kubelet capz-conf-krg8l} Created: Created container kube-proxy
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:17 +0000 UTC - event for kube-proxy-windows-69qmt: {kubelet capz-conf-krg8l} Started: Started container kube-proxy
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:21 +0000 UTC - event for calico-node-windows-pfnw6: {kubelet capz-conf-krg8l} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 3.8590718s (3.8590718s including waiting)
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:21 +0000 UTC - event for calico-node-windows-pfnw6: {kubelet capz-conf-krg8l} Started: Started container install-cni
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:21 +0000 UTC - event for calico-node-windows-pfnw6: {kubelet capz-conf-krg8l} Created: Created container install-cni
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:22 +0000 UTC - event for calico-node-windows-jbdps: {kubelet capz-conf-d9m9m} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:22 +0000 UTC - event for containerd-logger-v2t6g: {kubelet capz-conf-d9m9m} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:22 +0000 UTC - event for kube-proxy-windows-8ntns: {kubelet capz-conf-d9m9m} Started: Started container kube-proxy
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:22 +0000 UTC - event for kube-proxy-windows-8ntns: {kubelet capz-conf-d9m9m} Created: Created container kube-proxy
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:22 +0000 UTC - event for kube-proxy-windows-8ntns: {kubelet capz-conf-d9m9m} Pulled: Container image "sigwindowstools/kube-proxy:v1.26.0-beta.0.70_f5d6ffc86771e2-calico-hostprocess" already present on machine
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:23 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-dlhrr
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:23 +0000 UTC - event for csi-proxy-dlhrr: {kubelet capz-conf-krg8l} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:23 +0000 UTC - event for csi-proxy-dlhrr: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-dlhrr to capz-conf-krg8l
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:25 +0000 UTC - event for containerd-logger-4mn65: {kubelet capz-conf-krg8l} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 3.7481686s (7.5609061s including waiting)
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:25 +0000 UTC - event for containerd-logger-v2t6g: {kubelet capz-conf-d9m9m} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 3.2678228s (3.2683104s including waiting)
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:27 +0000 UTC - event for calico-node-windows-pfnw6: {kubelet capz-conf-krg8l} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:29 +0000 UTC - event for calico-node-windows-jbdps: {kubelet capz-conf-d9m9m} Created: Created container install-cni
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:29 +0000 UTC - event for calico-node-windows-jbdps: {kubelet capz-conf-d9m9m} Started: Started container install-cni
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:29 +0000 UTC - event for calico-node-windows-jbdps: {kubelet capz-conf-d9m9m} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 3.7410022s (6.9828282s including waiting)
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:30 +0000 UTC - event for containerd-logger-v2t6g: {kubelet capz-conf-d9m9m} Created: Created container containerd-logger
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:31 +0000 UTC - event for containerd-logger-4mn65: {kubelet capz-conf-krg8l} Created: Created container containerd-logger
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:31 +0000 UTC - event for containerd-logger-v2t6g: {kubelet capz-conf-d9m9m} Started: Started container containerd-logger
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:31 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-85r8d
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:31 +0000 UTC - event for csi-proxy-85r8d: {kubelet capz-conf-d9m9m} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:31 +0000 UTC - event for csi-proxy-85r8d: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-85r8d to capz-conf-d9m9m
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:32 +0000 UTC - event for containerd-logger-4mn65: {kubelet capz-conf-krg8l} Started: Started container containerd-logger
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:35 +0000 UTC - event for calico-node-windows-jbdps: {kubelet capz-conf-d9m9m} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:39 +0000 UTC - event for csi-proxy-dlhrr: {kubelet capz-conf-krg8l} Started: Started container csi-proxy
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:39 +0000 UTC - event for csi-proxy-dlhrr: {kubelet capz-conf-krg8l} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 14.5070234s (15.7278643s including waiting)
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:39 +0000 UTC - event for csi-proxy-dlhrr: {kubelet capz-conf-krg8l} Created: Created container csi-proxy
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:43 +0000 UTC - event for calico-node-windows-pfnw6: {kubelet capz-conf-krg8l} Created: Created container calico-node-startup
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:43 +0000 UTC - event for calico-node-windows-pfnw6: {kubelet capz-conf-krg8l} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 356.0058ms (356.0058ms including waiting)
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:43 +0000 UTC - event for calico-node-windows-pfnw6: {kubelet capz-conf-krg8l} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:43 +0000 UTC - event for calico-node-windows-pfnw6: {kubelet capz-conf-krg8l} Started: Started container calico-node-startup
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:43 +0000 UTC - event for calico-node-windows-pfnw6: {kubelet capz-conf-krg8l} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 3.763067s (16.1574272s including waiting)
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:45 +0000 UTC - event for csi-proxy-85r8d: {kubelet capz-conf-d9m9m} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 13.5302989s (13.5302989s including waiting)
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:45 +0000 UTC - event for csi-proxy-85r8d: {kubelet capz-conf-d9m9m} Started: Started container csi-proxy
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:45 +0000 UTC - event for csi-proxy-85r8d: {kubelet capz-conf-d9m9m} Created: Created container csi-proxy
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:49 +0000 UTC - event for calico-node-windows-jbdps: {kubelet capz-conf-d9m9m} Created: Created container calico-node-startup
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:49 +0000 UTC - event for calico-node-windows-jbdps: {kubelet capz-conf-d9m9m} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 3.6721238s (13.8824834s including waiting)
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:49 +0000 UTC - event for calico-node-windows-jbdps: {kubelet capz-conf-d9m9m} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 364.0605ms (364.0605ms including waiting)
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:49 +0000 UTC - event for calico-node-windows-jbdps: {kubelet capz-conf-d9m9m} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:49 +0000 UTC - event for calico-node-windows-jbdps: {kubelet capz-conf-d9m9m} Started: Started container calico-node-startup
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:49 +0000 UTC - event for calico-node-windows-pfnw6: {kubelet capz-conf-krg8l} Created: Created container calico-node-felix
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:49 +0000 UTC - event for calico-node-windows-pfnw6: {kubelet capz-conf-krg8l} Started: Started container calico-node-felix
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:55 +0000 UTC - event for calico-node-windows-jbdps: {kubelet capz-conf-d9m9m} Created: Created container calico-node-felix
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:10:55 +0000 UTC - event for calico-node-windows-jbdps: {kubelet capz-conf-d9m9m} Started: Started container calico-node-felix
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:11:09 +0000 UTC - event for calico-node-windows-pfnw6: {kubelet capz-conf-krg8l} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 328.8136ms (328.8136ms including waiting)
Nov 14 19:21:40.166: INFO: At 2022-11-14 19:11:16 +0000 UTC - event for calico-node-windows-jbdps: {kubelet capz-conf-d9m9m} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 328.0602ms (328.0602ms including waiting)
Nov 14 19:21:40.221: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 14 19:21:40.221: INFO: calico-kube-controllers-657b584867-jtbsh capz-conf-185r3j-control-plane-r6sjn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:01 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:26 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:26 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:01 +0000 UTC }]
Nov 14 19:21:40.221: INFO: calico-node-4h45g capz-conf-185r3j-control-plane-r6sjn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:01 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:11 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:11 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:07:47 +0000 UTC }]
Nov 14 19:21:40.221: INFO: calico-node-windows-jbdps capz-conf-d9m9m Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:35 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:11:22 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:11:22 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:06 +0000 UTC }]
Nov 14 19:21:40.221: INFO: calico-node-windows-pfnw6 capz-conf-krg8l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:27 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:11:15 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:11:15 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:01 +0000 UTC }]
Nov 14 19:21:40.221: INFO: containerd-logger-4mn65 capz-conf-krg8l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:01 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:32 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:32 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:01 +0000 UTC }]
Nov 14 19:21:40.221: INFO: containerd-logger-v2t6g capz-conf-d9m9m Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:06 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:32 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:32 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:05 +0000 UTC }]
Nov 14 19:21:40.221: INFO: coredns-787d4945fb-28shf capz-conf-185r3j-control-plane-r6sjn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:01 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:31 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:31 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:01 +0000 UTC }]
Nov 14 19:21:40.221: INFO: coredns-787d4945fb-g55nf capz-conf-185r3j-control-plane-r6sjn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:01 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:31 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:31 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:01 +0000 UTC }]
Nov 14 19:21:40.221: INFO: csi-proxy-85r8d capz-conf-d9m9m Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:31 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:46 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:46 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:31 +0000 UTC }]
Nov 14 19:21:40.221: INFO: csi-proxy-dlhrr capz-conf-krg8l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:23 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:40 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:40 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:23 +0000 UTC }]
Nov 14 19:21:40.221: INFO: etcd-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:07:15 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:07:25 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:07:25 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:07:15 +0000 UTC }]
Nov 14 19:21:40.221: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:40.221: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:40.221: INFO: kube-proxy-2cjlb capz-conf-185r3j-control-plane-r6sjn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:07:19 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:07:22 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:07:22 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:07:19 +0000 UTC }]
Nov 14 19:21:40.221: INFO: kube-proxy-windows-69qmt capz-conf-krg8l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:01 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:18 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:18 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:01 +0000 UTC }]
Nov 14 19:21:40.221: INFO: kube-proxy-windows-8ntns capz-conf-d9m9m Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:06 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:23 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:23 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:10:05 +0000 UTC }]
Nov 14 19:21:40.221: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Nov 14 19:21:40.221: INFO: metrics-server-c9574f845-26vvh capz-conf-185r3j-control-plane-r6sjn Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:01 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:42 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:42 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-14 19:08:01 +0000 UTC }]
Nov 14 19:21:40.222: INFO:
Nov 14 19:21:40.715: INFO:
Logging node info for node capz-conf-185r3j-control-plane-r6sjn
Nov 14 19:21:40.907: INFO: Node Info: &Node{ObjectMeta:{capz-conf-185r3j-control-plane-r6sjn 58f2966c-10a3-4f1e-9b0e-28203b15ba42 1816 0 2022-11-14 19:07:12 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:canadacentral failure-domain.beta.kubernetes.io/zone:canadacentral-1 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-185r3j-control-plane-r6sjn kubernetes.io/os:linux node-role.kubernetes.io/control-plane: node.kubernetes.io/exclude-from-external-load-balancers: node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:canadacentral-1] map[cluster.x-k8s.io/cluster-name:capz-conf-185r3j cluster.x-k8s.io/cluster-namespace:capz-conf-185r3j cluster.x-k8s.io/machine:capz-conf-185r3j-control-plane-2bfs5 cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-185r3j-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.204.192 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2022-11-14 19:07:12 +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 19:07:13 +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 19:07:44 +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 19:08:01 +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 19:08:09 +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 19:18:59 +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-185r3j/providers/Microsoft.Compute/virtualMachines/capz-conf-185r3j-control-plane-r6sjn,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 19:08:09 +0000 UTC,LastTransitionTime:2022-11-14 19:08:09 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-14 19:18:59 +0000 UTC,LastTransitionTime:2022-11-14 19:06:52 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-14 19:18:59 +0000 UTC,LastTransitionTime:2022-11-14 19:06:52 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-14 19:18:59 +0000 UTC,LastTransitionTime:2022-11-14 19:06:52 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-14 19:18:59 +0000 UTC,LastTransitionTime:2022-11-14 19:08:01 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-185r3j-control-plane-r6sjn,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:c6875f8d2447477c887a0d4777b7565e,SystemUUID:0c8b4567-0798-fa47-9626-a88e806752f1,BootID:9d45fca4-06f0-4e77-ab8e-1209bfda7c79,KernelVersion:5.4.0-1091-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.26.0-beta.0.85+0050669549cb7e,KubeProxyVersion:v1.26.0-beta.0.85+0050669549cb7e,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:68fcb99ddf96af6982d95ba8aea4bf14dd45de0de9545d2da9f70f82f0caa189 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.26.0-beta.0.70_f5d6ffc86771e2],SizeBytes:35316561,},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:8cc57a32d18c7b4be25c7e9759fcf1a0106851c44c82659a26e7df734ac3d1d9 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.26.0-beta.0.70_f5d6ffc86771e2],SizeBytes:32240416,},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:0502e8ae1399bc1bf0aa61e8c2fbbd0299c6c0b320957c99501b559c7ef0ae30 gcr.io/k8s-staging-ci-images/kube-proxy:v1.26.0-beta.0.70_f5d6ffc86771e2],SizeBytes:21534795,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:36bf69cca1e96326bf7a76193471b79e2e19230594945925ad6fa24abf1f2f97 capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.85_0050669549cb7e],SizeBytes:21532936,},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:1f55bc7a9b0ad5691f134311b03f4ba7ca4c4c63ca2488bbbf0b53050c0b4eb3 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.26.0-beta.0.70_f5d6ffc86771e2],SizeBytes:17482650,},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 19:21:40.907: INFO:
Logging kubelet events for node capz-conf-185r3j-control-plane-r6sjn
Nov 14 19:21:41.105: INFO:
Logging pods the kubelet thinks is on node capz-conf-185r3j-control-plane-r6sjn
Nov 14 19:21:41.343: INFO: kube-apiserver-capz-conf-185r3j-control-plane-r6sjn started at <nil> (0+0 container statuses recorded)
Nov 14 19:21:41.343: INFO: coredns-787d4945fb-28shf started at 2022-11-14 19:08:01 +0000 UTC (0+1 container statuses recorded)
Nov 14 19:21:41.343: INFO: Container coredns ready: true, restart count 0
Nov 14 19:21:41.343: INFO: calico-kube-controllers-657b584867-jtbsh started at 2022-11-14 19:08:01 +0000 UTC (0+1 container statuses recorded)
Nov 14 19:21:41.343: INFO: Container calico-kube-controllers ready: true, restart count 0
Nov 14 19:21:41.343: INFO: metrics-server-c9574f845-26vvh started at 2022-11-14 19:08:01 +0000 UTC (0+1 container statuses recorded)
Nov 14 19:21:41.343: INFO: Container metrics-server ready: true, restart count 0
Nov 14 19:21:41.343: INFO: kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn started at <nil> (0+0 container statuses recorded)
Nov 14 19:21:41.343: INFO: etcd-capz-conf-185r3j-control-plane-r6sjn started at 2022-11-14 19:07:15 +0000 UTC (0+1 container statuses recorded)
Nov 14 19:21:41.343: INFO: Container etcd ready: true, restart count 0
Nov 14 19:21:41.343: INFO: calico-node-4h45g started at 2022-11-14 19:07:47 +0000 UTC (2+1 container statuses recorded)
Nov 14 19:21:41.343: INFO: Init container upgrade-ipam ready: true, restart count 0
Nov 14 19:21:41.343: INFO: Init container install-cni ready: true, restart count 0
Nov 14 19:21:41.343: INFO: Container calico-node ready: true, restart count 0
Nov 14 19:21:41.343: INFO: coredns-787d4945fb-g55nf started at 2022-11-14 19:08:01 +0000 UTC (0+1 container statuses recorded)
Nov 14 19:21:41.343: INFO: Container coredns ready: true, restart count 0
Nov 14 19:21:41.343: INFO: kube-scheduler-capz-conf-185r3j-control-plane-r6sjn started at <nil> (0+0 container statuses recorded)
Nov 14 19:21:41.343: INFO: kube-proxy-2cjlb started at 2022-11-14 19:07:19 +0000 UTC (0+1 container statuses recorded)
Nov 14 19:21:41.343: INFO: Container kube-proxy ready: true, restart count 0
Nov 14 19:21:41.947: INFO:
Latency metrics for node capz-conf-185r3j-control-plane-r6sjn
Nov 14 19:21:41.947: INFO:
Logging node info for node capz-conf-d9m9m
Nov 14 19:21:42.103: INFO: Node Info: &Node{ObjectMeta:{capz-conf-d9m9m 473b6944-f944-42e5-85a8-24da6c1a682f 2028 0 2022-11-14 19:10:05 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D4s_v3 beta.kubernetes.io/os:windows failure-domain.beta.kubernetes.io/region:canadacentral failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-d9m9m kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-185r3j cluster.x-k8s.io/cluster-namespace:capz-conf-185r3j cluster.x-k8s.io/machine:capz-conf-185r3j-md-win-cbc655675-cmfgh cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-185r3j-md-win-cbc655675 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.206.193 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:ca:30:cc volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet.exe Update v1 2022-11-14 19:10:05 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:node.kubernetes.io/windows-build":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kubeadm Update v1 2022-11-14 19:10:06 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kube-controller-manager Update v1 2022-11-14 19:10:31 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2022-11-14 19:11:13 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{},"f:projectcalico.org/VXLANTunnelMACAddr":{}}}} status} {manager Update v1 2022-11-14 19:11:27 +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":{}}}} } {kubelet.exe Update v1 2022-11-14 19:21:20 +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-185r3j/providers/Microsoft.Compute/virtualMachines/capz-conf-d9m9m,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 19:21:20 +0000 UTC,LastTransitionTime:2022-11-14 19:10:05 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-14 19:21:20 +0000 UTC,LastTransitionTime:2022-11-14 19:10:05 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-14 19:21:20 +0000 UTC,LastTransitionTime:2022-11-14 19:10:05 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-14 19:21:20 +0000 UTC,LastTransitionTime:2022-11-14 19:10:31 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-d9m9m,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-d9m9m,SystemUUID:8111BD0E-E915-43B6-B8F8-E2DF061E95E4,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.26.0-beta.0.85+0050669549cb7e-dirty,KubeProxyVersion:v1.26.0-beta.0.85+0050669549cb7e-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.70_f5d6ffc86771e2-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 19:21:42.103: INFO:
Logging kubelet events for node capz-conf-d9m9m
Nov 14 19:21:42.304: INFO:
Logging pods the kubelet thinks is on node capz-conf-d9m9m
Nov 14 19:21:42.832: INFO: containerd-logger-v2t6g started at 2022-11-14 19:10:06 +0000 UTC (0+1 container statuses recorded)
Nov 14 19:21:42.832: INFO: Container containerd-logger ready: true, restart count 0
Nov 14 19:21:42.832: INFO: kube-proxy-windows-8ntns started at 2022-11-14 19:10:06 +0000 UTC (0+1 container statuses recorded)
Nov 14 19:21:42.832: INFO: Container kube-proxy ready: true, restart count 0
Nov 14 19:21:42.832: INFO: calico-node-windows-jbdps started at 2022-11-14 19:10:06 +0000 UTC (1+2 container statuses recorded)
Nov 14 19:21:42.832: INFO: Init container install-cni ready: true, restart count 0
Nov 14 19:21:42.832: INFO: Container calico-node-felix ready: true, restart count 1
Nov 14 19:21:42.832: INFO: Container calico-node-startup ready: true, restart count 0
Nov 14 19:21:42.832: INFO: csi-proxy-85r8d started at 2022-11-14 19:10:31 +0000 UTC (0+1 container statuses recorded)
Nov 14 19:21:42.832: INFO: Container csi-proxy ready: true, restart count 0
Nov 14 19:21:43.141: INFO:
Latency metrics for node capz-conf-d9m9m
Nov 14 19:21:43.141: INFO:
Logging node info for node capz-conf-krg8l
Nov 14 19:21:43.310: INFO: Node Info: &Node{ObjectMeta:{capz-conf-krg8l 7db1919c-a81d-4bf5-a286-83e7df3aa71a 2018 0 2022-11-14 19:10:01 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D4s_v3 beta.kubernetes.io/os:windows failure-domain.beta.kubernetes.io/region:canadacentral failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-krg8l kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-185r3j cluster.x-k8s.io/cluster-namespace:capz-conf-185r3j cluster.x-k8s.io/machine:capz-conf-185r3j-md-win-cbc655675-5wpkz cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-185r3j-md-win-cbc655675 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.135.129 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:a0:71:b7 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-14 19:10:01 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-14 19:10:01 +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 19:10:23 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-14 19:10:56 +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 19:11:07 +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 19:21:14 +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-185r3j/providers/Microsoft.Compute/virtualMachines/capz-conf-krg8l,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 19:21:14 +0000 UTC,LastTransitionTime:2022-11-14 19:10:01 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-14 19:21:14 +0000 UTC,LastTransitionTime:2022-11-14 19:10:01 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-14 19:21:14 +0000 UTC,LastTransitionTime:2022-11-14 19:10:01 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-14 19:21:14 +0000 UTC,LastTransitionTime:2022-11-14 19:10:23 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-krg8l,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-krg8l,SystemUUID:1801B747-B114-439C-BF0E-F7E052904CB6,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.26.0-beta.0.85+0050669549cb7e-dirty,KubeProxyVersion:v1.26.0-beta.0.85+0050669549cb7e-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.70_f5d6ffc86771e2-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 19:21:43.310: INFO:
Logging kubelet events for node capz-conf-krg8l
Nov 14 19:21:43.504: INFO:
Logging pods the kubelet thinks is on node capz-conf-krg8l
Nov 14 19:21:43.711: INFO: kube-proxy-windows-69qmt started at 2022-11-14 19:10:01 +0000 UTC (0+1 container statuses recorded)
Nov 14 19:21:43.711: INFO: Container kube-proxy ready: true, restart count 0
Nov 14 19:21:43.711: INFO: containerd-logger-4mn65 started at 2022-11-14 19:10:01 +0000 UTC (0+1 container statuses recorded)
Nov 14 19:21:43.711: INFO: Container containerd-logger ready: true, restart count 0
Nov 14 19:21:43.711: INFO: calico-node-windows-pfnw6 started at 2022-11-14 19:10:01 +0000 UTC (1+2 container statuses recorded)
Nov 14 19:21:43.711: INFO: Init container install-cni ready: true, restart count 0
Nov 14 19:21:43.711: INFO: Container calico-node-felix ready: true, restart count 1
Nov 14 19:21:43.711: INFO: Container calico-node-startup ready: true, restart count 0
Nov 14 19:21:43.711: INFO: csi-proxy-dlhrr started at 2022-11-14 19:10:23 +0000 UTC (0+1 container statuses recorded)
Nov 14 19:21:43.711: INFO: Container csi-proxy ready: true, restart count 0
Nov 14 19:21:44.347: INFO:
Latency metrics for node capz-conf-krg8l
Nov 14 19:21:44.514: INFO: Running kubectl logs on non-ready containers in kube-system
Nov 14 19:21:44.904: INFO: Failed to get logs of pod kube-apiserver-capz-conf-185r3j-control-plane-r6sjn, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-185r3j-control-plane-r6sjn)
Nov 14 19:21:44.904: INFO: Logs of kube-system/kube-apiserver-capz-conf-185r3j-control-plane-r6sjn:kube-apiserver on node capz-conf-185r3j-control-plane-r6sjn
Nov 14 19:21:44.904: INFO: : STARTLOG
ENDLOG for container kube-system:kube-apiserver-capz-conf-185r3j-control-plane-r6sjn:kube-apiserver
Nov 14 19:21:45.304: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn)
Nov 14 19:21:45.304: INFO: Logs of kube-system/kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn:kube-controller-manager on node capz-conf-185r3j-control-plane-r6sjn
Nov 14 19:21:45.304: INFO: : STARTLOG
ENDLOG for container kube-system:kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn:kube-controller-manager
Nov 14 19:21:45.704: INFO: Failed to get logs of pod kube-scheduler-capz-conf-185r3j-control-plane-r6sjn, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-185r3j-control-plane-r6sjn)
Nov 14 19:21:45.704: INFO: Logs of kube-system/kube-scheduler-capz-conf-185r3j-control-plane-r6sjn:kube-scheduler on node capz-conf-185r3j-control-plane-r6sjn
Nov 14 19:21:45.704: INFO: : STARTLOG
ENDLOG for container kube-system:kube-scheduler-capz-conf-185r3j-control-plane-r6sjn:kube-scheduler
Nov 14 19:21:45.704: 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-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
kube-controller-manager-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
kube-scheduler-capz-conf-185r3j-control-plane-r6sjn capz-conf-185r3j-control-plane-r6sjn Pending []
Full Stack Trace
k8s.io/kubernetes/test/e2e.setupSuite({0x7f63e00e1db8, 0xc0022caec0})
test/e2e/e2e.go:249 +0x5bf
k8s.io/kubernetes/test/e2e.glob..func1({0x7f63e00e1db8, 0xc0022caec0})
test/e2e/e2e.go:81 +0xaa
reflect.Value.call({0x6855240?, 0x78ae028?, 0x0?}, {0x75d039a, 0x4}, {0xc000b61f38, 0x1, 0x0?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x6855240?, 0x78ae028?, 0x0?}, {0xc000b61f38?, 0x0?, 0x0?})
/usr/local/go/src/reflect/value.go:368 +0xbc
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:77
from junit.kubetest.01.xml
Filter through log files | View test history on testgrid
Kubernetes e2e suite [ReportAfterSuite] Kubernetes e2e suite report
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
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