PR #115004 pull-kubernetes-e2e-capz-conformance #1613430912656084992
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | Rajalakshmi-Girish: Automated cherry pick of #114078: Explicitly call rand.Seed() method |
| Result | SUCCESS |
| Tests | 25 failed / 27 succeeded |
| Started | |
| Elapsed | 53m22s |
| Revision | fce4a9ad7588311664319d8dd7b45fbe06bc9764 |
| Refs |
115004 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[SynchronizedBeforeSuite\]$'
test/e2e/e2e.go:76
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:76
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:76
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:76
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:76
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:76
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:76
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:76
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:76
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:76
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:76
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:76
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:76
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:76
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:76
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:76
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:76
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:76
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:76
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:76
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:76
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:76
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:80 k8s.io/kubernetes/test/e2e.glob..func1() test/e2e/e2e.go:80 +0x8ffrom junit.kubetest.01.xml
{"msg":"Test Suite starting","completed":0,"skipped":0,"failed":0} [SynchronizedBeforeSuite] TOP-LEVEL test/e2e/e2e.go:76 Jan 12 07:39:54.228: INFO: >>> kubeConfig: /tmp/kubeconfig Jan 12 07:39:54.231: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable Jan 12 07:39:54.422: INFO: Condition Ready of node capz-conf-fg0xvh-md-0-fdcn2 is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule <nil>} {node.kubernetes.io/not-ready NoExecute 2023-01-12 07:39:20 +0000 UTC}]. Failure Jan 12 07:39:54.422: INFO: Condition Ready of node capz-conf-fg0xvh-md-0-ssgl2 is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready NoSchedule <nil>} {node.kubernetes.io/not-ready NoExecute 2023-01-12 07:39:44 +0000 UTC}]. Failure Jan 12 07:39:54.422: INFO: Unschedulable nodes= 2, maximum value for starting tests= 0 Jan 12 07:39:54.422: INFO: -> Node capz-conf-fg0xvh-md-0-fdcn2 [[[ Ready=false, Network(available)=true, Taints=[{node.kubernetes.io/not-ready NoSchedule <nil>} {node.kubernetes.io/not-ready NoExecute 2023-01-12 07:39:20 +0000 UTC}], NonblockingTaints=node-role.kubernetes.io/control-plane,node-role.kubernetes.io/master ]]] Jan 12 07:39:54.422: INFO: -> Node capz-conf-fg0xvh-md-0-ssgl2 [[[ Ready=false, Network(available)=false, Taints=[{node.kubernetes.io/not-ready NoSchedule <nil>} {node.kubernetes.io/not-ready NoExecute 2023-01-12 07:39:44 +0000 UTC}], NonblockingTaints=node-role.kubernetes.io/control-plane,node-role.kubernetes.io/master ]]] Jan 12 07:39:54.422: INFO: ==== node wait: 1 out of 3 nodes are ready, max notReady allowed 0. Need 2 more before starting. Jan 12 07:40:24.469: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready Jan 12 07:40:24.668: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:24.668: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:24.668: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:24.668: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) Jan 12 07:40:24.668: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:24.668: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:24.668: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:24.668: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:24.668: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:24.668: INFO: Jan 12 07:40:26.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:26.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:26.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:26.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (2 seconds elapsed) Jan 12 07:40:26.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:26.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:26.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:26.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:26.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:26.800: INFO: Jan 12 07:40:28.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:28.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:28.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:28.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (4 seconds elapsed) Jan 12 07:40:28.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:28.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:28.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:28.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:28.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:28.797: INFO: Jan 12 07:40:30.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:30.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:30.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:30.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (6 seconds elapsed) Jan 12 07:40:30.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:30.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:30.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:30.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:30.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:30.797: INFO: Jan 12 07:40:32.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:32.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:32.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:32.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (8 seconds elapsed) Jan 12 07:40:32.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:32.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:32.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:32.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:32.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:32.795: INFO: Jan 12 07:40:34.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:34.799: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:34.799: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:34.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (10 seconds elapsed) Jan 12 07:40:34.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:34.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:34.799: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:34.799: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:34.799: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:34.799: INFO: Jan 12 07:40:36.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:36.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:36.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:36.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (12 seconds elapsed) Jan 12 07:40:36.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:36.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:36.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:36.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:36.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:36.797: INFO: Jan 12 07:40:38.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:38.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:38.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:38.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (14 seconds elapsed) Jan 12 07:40:38.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:38.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:38.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:38.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:38.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:38.798: INFO: Jan 12 07:40:40.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:40.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:40.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:40.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (16 seconds elapsed) Jan 12 07:40:40.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:40.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:40.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:40.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:40.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:40.795: INFO: Jan 12 07:40:42.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:42.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:42.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:42.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (18 seconds elapsed) Jan 12 07:40:42.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:42.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:42.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:42.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:42.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:42.796: INFO: Jan 12 07:40:44.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:44.799: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:44.799: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:44.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed) Jan 12 07:40:44.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:44.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:44.799: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:44.799: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:44.799: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:44.799: INFO: Jan 12 07:40:46.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:46.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:46.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:46.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (22 seconds elapsed) Jan 12 07:40:46.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:46.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:46.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:46.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:46.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:46.795: INFO: Jan 12 07:40:48.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:48.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:48.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:48.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (24 seconds elapsed) Jan 12 07:40:48.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:48.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:48.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:48.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:48.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:48.797: INFO: Jan 12 07:40:50.806: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:50.806: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:50.806: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:50.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (26 seconds elapsed) Jan 12 07:40:50.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:50.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:50.806: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:50.806: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:50.806: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:50.806: INFO: Jan 12 07:40:52.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:52.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:52.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:52.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (28 seconds elapsed) Jan 12 07:40:52.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:52.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:52.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:52.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:52.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:52.796: INFO: Jan 12 07:40:54.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:54.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:54.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:54.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (30 seconds elapsed) Jan 12 07:40:54.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:54.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:54.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:54.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:54.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:54.797: INFO: Jan 12 07:40:56.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:56.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:56.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:56.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (32 seconds elapsed) Jan 12 07:40:56.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:56.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:56.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:56.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:56.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:56.796: INFO: Jan 12 07:40:58.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:58.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:58.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:40:58.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (34 seconds elapsed) Jan 12 07:40:58.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:40:58.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:40:58.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:58.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:58.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:40:58.796: INFO: Jan 12 07:41:00.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:00.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:00.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:00.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (36 seconds elapsed) Jan 12 07:41:00.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:00.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:00.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:00.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:00.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:00.797: INFO: Jan 12 07:41:02.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:02.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:02.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:02.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (38 seconds elapsed) Jan 12 07:41:02.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:02.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:02.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:02.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:02.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:02.794: INFO: Jan 12 07:41:04.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:04.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:04.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:04.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (40 seconds elapsed) Jan 12 07:41:04.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:04.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:04.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:04.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:04.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:04.795: INFO: Jan 12 07:41:06.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:06.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:06.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:06.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (42 seconds elapsed) Jan 12 07:41:06.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:06.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:06.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:06.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:06.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:06.797: INFO: Jan 12 07:41:08.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:08.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:08.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:08.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (44 seconds elapsed) Jan 12 07:41:08.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:08.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:08.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:08.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:08.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:08.795: INFO: Jan 12 07:41:10.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:10.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:10.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:10.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (46 seconds elapsed) Jan 12 07:41:10.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:10.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:10.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:10.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:10.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:10.794: INFO: Jan 12 07:41:12.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:12.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:12.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:12.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (48 seconds elapsed) Jan 12 07:41:12.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:12.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:12.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:12.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:12.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:12.796: INFO: Jan 12 07:41:14.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:14.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:14.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:14.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (50 seconds elapsed) Jan 12 07:41:14.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:14.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:14.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:14.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:14.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:14.794: INFO: Jan 12 07:41:16.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:16.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:16.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:16.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (52 seconds elapsed) Jan 12 07:41:16.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:16.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:16.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:16.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:16.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:16.795: INFO: Jan 12 07:41:18.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:18.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:18.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:18.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (54 seconds elapsed) Jan 12 07:41:18.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:18.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:18.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:18.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:18.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:18.795: INFO: Jan 12 07:41:20.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:20.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:20.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:20.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (56 seconds elapsed) Jan 12 07:41:20.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:20.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:20.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:20.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:20.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:20.795: INFO: Jan 12 07:41:22.806: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:22.806: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:22.806: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:22.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (58 seconds elapsed) Jan 12 07:41:22.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:22.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:22.806: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:22.806: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:22.806: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:22.806: INFO: Jan 12 07:41:24.808: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:24.808: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:24.808: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:24.809: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (60 seconds elapsed) Jan 12 07:41:24.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:24.809: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:24.809: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:24.809: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:24.809: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:24.809: INFO: Jan 12 07:41:26.806: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:26.806: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:26.806: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:26.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (62 seconds elapsed) Jan 12 07:41:26.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:26.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:26.806: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:26.806: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:26.806: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:26.806: INFO: Jan 12 07:41:28.809: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:28.809: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:28.809: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:28.809: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (64 seconds elapsed) Jan 12 07:41:28.809: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:28.809: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:28.809: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:28.810: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:28.810: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:28.810: INFO: Jan 12 07:41:30.802: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:30.802: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:30.802: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:30.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (66 seconds elapsed) Jan 12 07:41:30.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:30.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:30.802: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:30.802: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:30.802: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:30.802: INFO: Jan 12 07:41:32.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:32.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:32.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:32.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (68 seconds elapsed) Jan 12 07:41:32.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:32.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:32.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:32.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:32.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:32.795: INFO: Jan 12 07:41:34.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:34.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:34.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:34.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (70 seconds elapsed) Jan 12 07:41:34.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:34.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:34.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:34.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:34.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:34.796: INFO: Jan 12 07:41:36.815: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:36.816: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:36.816: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:36.816: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (72 seconds elapsed) Jan 12 07:41:36.816: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:36.816: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:36.816: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:36.816: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:36.816: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:36.816: INFO: Jan 12 07:41:38.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:38.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:38.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:38.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (74 seconds elapsed) Jan 12 07:41:38.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:38.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:38.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:38.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:38.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:38.796: INFO: Jan 12 07:41:40.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:40.799: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:40.799: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:40.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (76 seconds elapsed) Jan 12 07:41:40.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:40.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:40.799: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:40.799: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:40.799: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:40.799: INFO: Jan 12 07:41:42.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:42.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:42.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:42.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (78 seconds elapsed) Jan 12 07:41:42.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:42.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:42.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:42.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:42.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:42.800: INFO: Jan 12 07:41:44.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:44.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:44.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:44.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (80 seconds elapsed) Jan 12 07:41:44.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:44.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:44.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:44.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:44.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:44.795: INFO: Jan 12 07:41:46.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:46.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:46.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:46.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (82 seconds elapsed) Jan 12 07:41:46.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:46.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:46.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:46.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:46.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:46.797: INFO: Jan 12 07:41:48.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:48.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:48.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:48.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (84 seconds elapsed) Jan 12 07:41:48.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:48.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:48.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:48.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:48.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:48.794: INFO: Jan 12 07:41:50.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:50.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:50.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:50.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (86 seconds elapsed) Jan 12 07:41:50.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:50.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:50.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:50.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:50.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:50.798: INFO: Jan 12 07:41:52.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:52.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:52.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:52.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (88 seconds elapsed) Jan 12 07:41:52.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:52.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:52.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:52.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:52.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:52.795: INFO: Jan 12 07:41:54.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:54.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:54.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:54.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (90 seconds elapsed) Jan 12 07:41:54.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:54.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:54.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:54.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:54.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:54.795: INFO: Jan 12 07:41:56.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:56.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:56.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:56.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (92 seconds elapsed) Jan 12 07:41:56.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:56.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:56.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:56.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:56.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:56.796: INFO: Jan 12 07:41:58.793: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:58.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:58.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:41:58.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (94 seconds elapsed) Jan 12 07:41:58.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:41:58.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:41:58.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:58.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:58.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:41:58.794: INFO: Jan 12 07:42:00.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:00.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:00.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:00.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (96 seconds elapsed) Jan 12 07:42:00.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:00.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:00.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:00.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:00.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:00.794: INFO: Jan 12 07:42:02.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:02.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:02.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:02.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (98 seconds elapsed) Jan 12 07:42:02.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:02.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:02.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:02.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:02.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:02.796: INFO: Jan 12 07:42:04.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:04.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:04.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:04.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (100 seconds elapsed) Jan 12 07:42:04.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:04.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:04.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:04.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:04.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:04.794: INFO: Jan 12 07:42:06.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:06.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:06.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:06.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (102 seconds elapsed) Jan 12 07:42:06.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:06.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:06.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:06.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:06.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:06.798: INFO: Jan 12 07:42:08.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:08.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:08.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:08.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (104 seconds elapsed) Jan 12 07:42:08.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:08.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:08.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:08.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:08.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:08.795: INFO: Jan 12 07:42:10.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:10.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:10.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:10.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (106 seconds elapsed) Jan 12 07:42:10.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:10.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:10.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:10.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:10.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:10.795: INFO: Jan 12 07:42:12.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:12.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:12.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:12.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (108 seconds elapsed) Jan 12 07:42:12.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:12.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:12.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:12.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:12.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:12.794: INFO: Jan 12 07:42:14.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:14.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:14.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:14.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (110 seconds elapsed) Jan 12 07:42:14.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:14.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:14.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:14.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:14.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:14.797: INFO: Jan 12 07:42:16.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:16.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:16.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:16.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (112 seconds elapsed) Jan 12 07:42:16.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:16.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:16.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:16.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:16.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:16.797: INFO: Jan 12 07:42:18.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:18.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:18.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:18.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (114 seconds elapsed) Jan 12 07:42:18.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:18.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:18.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:18.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:18.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:18.795: INFO: Jan 12 07:42:20.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:20.799: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:20.799: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:20.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (116 seconds elapsed) Jan 12 07:42:20.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:20.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:20.799: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:20.799: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:20.799: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:20.799: INFO: Jan 12 07:42:22.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:22.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:22.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:22.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (118 seconds elapsed) Jan 12 07:42:22.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:22.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:22.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:22.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:22.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:22.794: INFO: Jan 12 07:42:24.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:24.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:24.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:24.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (120 seconds elapsed) Jan 12 07:42:24.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:24.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:24.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:24.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:24.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:24.795: INFO: Jan 12 07:42:26.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:26.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:26.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:26.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (122 seconds elapsed) Jan 12 07:42:26.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:26.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:26.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:26.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:26.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:26.795: INFO: Jan 12 07:42:28.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:28.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:28.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:28.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (124 seconds elapsed) Jan 12 07:42:28.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:28.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:28.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:28.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:28.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:28.800: INFO: Jan 12 07:42:30.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:30.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:30.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:30.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (126 seconds elapsed) Jan 12 07:42:30.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:30.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:30.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:30.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:30.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:30.795: INFO: Jan 12 07:42:32.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:32.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:32.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:32.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (128 seconds elapsed) Jan 12 07:42:32.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:32.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:32.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:32.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:32.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:32.798: INFO: Jan 12 07:42:34.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:34.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:34.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:34.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (130 seconds elapsed) Jan 12 07:42:34.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:34.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:34.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:34.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:34.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:34.796: INFO: Jan 12 07:42:36.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:36.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:36.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:36.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (132 seconds elapsed) Jan 12 07:42:36.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:36.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:36.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:36.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:36.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:36.800: INFO: Jan 12 07:42:38.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:38.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:38.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:38.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (134 seconds elapsed) Jan 12 07:42:38.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:38.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:38.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:38.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:38.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:38.797: INFO: Jan 12 07:42:40.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:40.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:40.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:40.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (136 seconds elapsed) Jan 12 07:42:40.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:40.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:40.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:40.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:40.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:40.794: INFO: Jan 12 07:42:42.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:42.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:42.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:42.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (138 seconds elapsed) Jan 12 07:42:42.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:42.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:42.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:42.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:42.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:42.795: INFO: Jan 12 07:42:44.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:44.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:44.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:44.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (140 seconds elapsed) Jan 12 07:42:44.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:44.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:44.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:44.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:44.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:44.796: INFO: Jan 12 07:42:46.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:46.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:46.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:46.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (142 seconds elapsed) Jan 12 07:42:46.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:46.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:46.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:46.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:46.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:46.795: INFO: Jan 12 07:42:48.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:48.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:48.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:48.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (144 seconds elapsed) Jan 12 07:42:48.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:48.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:48.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:48.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:48.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:48.794: INFO: Jan 12 07:42:50.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:50.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:50.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:50.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (146 seconds elapsed) Jan 12 07:42:50.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:50.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:50.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:50.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:50.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:50.795: INFO: Jan 12 07:42:52.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:52.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:52.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:52.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (148 seconds elapsed) Jan 12 07:42:52.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:52.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:52.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:52.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:52.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:52.794: INFO: Jan 12 07:42:54.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:54.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:54.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:54.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (150 seconds elapsed) Jan 12 07:42:54.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:54.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:54.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:54.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:54.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:54.795: INFO: Jan 12 07:42:56.851: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:56.851: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:56.851: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:56.851: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (152 seconds elapsed) Jan 12 07:42:56.851: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:56.851: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:56.851: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:56.851: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:56.851: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:56.851: INFO: Jan 12 07:42:58.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:58.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:58.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:42:58.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (154 seconds elapsed) Jan 12 07:42:58.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:42:58.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:42:58.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:58.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:58.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:42:58.795: INFO: Jan 12 07:43:00.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:00.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:00.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:00.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (156 seconds elapsed) Jan 12 07:43:00.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:00.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:00.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:00.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:00.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:00.795: INFO: Jan 12 07:43:02.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:02.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:02.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:02.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (158 seconds elapsed) Jan 12 07:43:02.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:02.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:02.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:02.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:02.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:02.794: INFO: Jan 12 07:43:04.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:04.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:04.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:04.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (160 seconds elapsed) Jan 12 07:43:04.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:04.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:04.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:04.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:04.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:04.795: INFO: Jan 12 07:43:06.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:06.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:06.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:06.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (162 seconds elapsed) Jan 12 07:43:06.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:06.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:06.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:06.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:06.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:06.795: INFO: Jan 12 07:43:08.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:08.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:08.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:08.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (164 seconds elapsed) Jan 12 07:43:08.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:08.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:08.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:08.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:08.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:08.795: INFO: Jan 12 07:43:10.792: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:10.792: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:10.792: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:10.792: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (166 seconds elapsed) Jan 12 07:43:10.792: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:10.792: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:10.792: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:10.792: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:10.792: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:10.792: INFO: Jan 12 07:43:12.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:12.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:12.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:12.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (168 seconds elapsed) Jan 12 07:43:12.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:12.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:12.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:12.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:12.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:12.794: INFO: Jan 12 07:43:14.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:14.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:14.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:14.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (170 seconds elapsed) Jan 12 07:43:14.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:14.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:14.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:14.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:14.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:14.795: INFO: Jan 12 07:43:16.807: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:16.807: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:16.807: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:16.807: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (172 seconds elapsed) Jan 12 07:43:16.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:16.807: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:16.807: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:16.807: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:16.807: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:16.807: INFO: Jan 12 07:43:18.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:18.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:18.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:18.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (174 seconds elapsed) Jan 12 07:43:18.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:18.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:18.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:18.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:18.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:18.796: INFO: Jan 12 07:43:20.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:20.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:20.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:20.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (176 seconds elapsed) Jan 12 07:43:20.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:20.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:20.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:20.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:20.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:20.795: INFO: Jan 12 07:43:22.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:22.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:22.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:22.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (178 seconds elapsed) Jan 12 07:43:22.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:22.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:22.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:22.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:22.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:22.795: INFO: Jan 12 07:43:24.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:24.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:24.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:24.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (180 seconds elapsed) Jan 12 07:43:24.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:24.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:24.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:24.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:24.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:24.797: INFO: Jan 12 07:43:26.810: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:26.810: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:26.810: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:26.810: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (182 seconds elapsed) Jan 12 07:43:26.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:26.810: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:26.810: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:26.810: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:26.810: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:26.810: INFO: Jan 12 07:43:28.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:28.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:28.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:28.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (184 seconds elapsed) Jan 12 07:43:28.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:28.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:28.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:28.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:28.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:28.800: INFO: Jan 12 07:43:30.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:30.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:30.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:30.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (186 seconds elapsed) Jan 12 07:43:30.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:30.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:30.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:30.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:30.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:30.796: INFO: Jan 12 07:43:32.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:32.799: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:32.799: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:32.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (188 seconds elapsed) Jan 12 07:43:32.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:32.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:32.799: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:32.799: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:32.799: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:32.799: INFO: Jan 12 07:43:34.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:34.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:34.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:34.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (190 seconds elapsed) Jan 12 07:43:34.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:34.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:34.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:34.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:34.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:34.796: INFO: Jan 12 07:43:36.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:36.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:36.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:36.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (192 seconds elapsed) Jan 12 07:43:36.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:36.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:36.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:36.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:36.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:36.797: INFO: Jan 12 07:43:38.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:38.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:38.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:38.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (194 seconds elapsed) Jan 12 07:43:38.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:38.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:38.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:38.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:38.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:38.797: INFO: Jan 12 07:43:40.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:40.799: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:40.799: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:40.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (196 seconds elapsed) Jan 12 07:43:40.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:40.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:40.799: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:40.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:40.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:40.800: INFO: Jan 12 07:43:42.801: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:42.801: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:42.801: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:42.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (198 seconds elapsed) Jan 12 07:43:42.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:42.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:42.801: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:42.801: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:42.801: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:42.801: INFO: Jan 12 07:43:44.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:44.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:44.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:44.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (200 seconds elapsed) Jan 12 07:43:44.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:44.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:44.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:44.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:44.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:44.796: INFO: Jan 12 07:43:46.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:46.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:46.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:46.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (202 seconds elapsed) Jan 12 07:43:46.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:46.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:46.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:46.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:46.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:46.797: INFO: Jan 12 07:43:48.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:48.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:48.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:48.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (204 seconds elapsed) Jan 12 07:43:48.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:48.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:48.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:48.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:48.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:48.794: INFO: Jan 12 07:43:50.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:50.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:50.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:50.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (206 seconds elapsed) Jan 12 07:43:50.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:50.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:50.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:50.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:50.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:50.794: INFO: Jan 12 07:43:52.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:52.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:52.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:52.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (208 seconds elapsed) Jan 12 07:43:52.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:52.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:52.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:52.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:52.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:52.796: INFO: Jan 12 07:43:54.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:54.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:54.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:54.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (210 seconds elapsed) Jan 12 07:43:54.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:54.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:54.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:54.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:54.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:54.795: INFO: Jan 12 07:43:56.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:56.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:56.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:56.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (212 seconds elapsed) Jan 12 07:43:56.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:56.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:56.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:56.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:56.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:56.798: INFO: Jan 12 07:43:58.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:58.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:58.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:43:58.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (214 seconds elapsed) Jan 12 07:43:58.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:43:58.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:43:58.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:58.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:58.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:43:58.795: INFO: Jan 12 07:44:00.793: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:00.793: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:00.793: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:00.793: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (216 seconds elapsed) Jan 12 07:44:00.793: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:00.793: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:00.793: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:00.793: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:00.793: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:00.793: INFO: Jan 12 07:44:02.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:02.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:02.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:02.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (218 seconds elapsed) Jan 12 07:44:02.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:02.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:02.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:02.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:02.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:02.796: INFO: Jan 12 07:44:04.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:04.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:04.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:04.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (220 seconds elapsed) Jan 12 07:44:04.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:04.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:04.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:04.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:04.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:04.798: INFO: Jan 12 07:44:06.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:06.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:06.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:06.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (222 seconds elapsed) Jan 12 07:44:06.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:06.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:06.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:06.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:06.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:06.794: INFO: Jan 12 07:44:08.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:08.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:08.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:08.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (224 seconds elapsed) Jan 12 07:44:08.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:08.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:08.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:08.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:08.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:08.796: INFO: Jan 12 07:44:10.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:10.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:10.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:10.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (226 seconds elapsed) Jan 12 07:44:10.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:10.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:10.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:10.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:10.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:10.797: INFO: Jan 12 07:44:12.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:12.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:12.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:12.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (228 seconds elapsed) Jan 12 07:44:12.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:12.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:12.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:12.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:12.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:12.794: INFO: Jan 12 07:44:14.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:14.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:14.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:14.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (230 seconds elapsed) Jan 12 07:44:14.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:14.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:14.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:14.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:14.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:14.794: INFO: Jan 12 07:44:16.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:16.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:16.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:16.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (232 seconds elapsed) Jan 12 07:44:16.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:16.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:16.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:16.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:16.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:16.795: INFO: Jan 12 07:44:18.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:18.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:18.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:18.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (234 seconds elapsed) Jan 12 07:44:18.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:18.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:18.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:18.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:18.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:18.794: INFO: Jan 12 07:44:20.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:20.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:20.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:20.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (236 seconds elapsed) Jan 12 07:44:20.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:20.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:20.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:20.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:20.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:20.796: INFO: Jan 12 07:44:22.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:22.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:22.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:22.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (238 seconds elapsed) Jan 12 07:44:22.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:22.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:22.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:22.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:22.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:22.796: INFO: Jan 12 07:44:24.803: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:24.803: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:24.803: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:24.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (240 seconds elapsed) Jan 12 07:44:24.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:24.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:24.803: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:24.803: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:24.803: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:24.803: INFO: Jan 12 07:44:26.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:26.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:26.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:26.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (242 seconds elapsed) Jan 12 07:44:26.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:26.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:26.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:26.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:26.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:26.797: INFO: Jan 12 07:44:28.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:28.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:28.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:28.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (244 seconds elapsed) Jan 12 07:44:28.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:28.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:28.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:28.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:28.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:28.797: INFO: Jan 12 07:44:30.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:30.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:30.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:30.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (246 seconds elapsed) Jan 12 07:44:30.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:30.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:30.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:30.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:30.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:30.796: INFO: Jan 12 07:44:32.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:32.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:32.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:32.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (248 seconds elapsed) Jan 12 07:44:32.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:32.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:32.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:32.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:32.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:32.795: INFO: Jan 12 07:44:34.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:34.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:34.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:34.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (250 seconds elapsed) Jan 12 07:44:34.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:34.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:34.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:34.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:34.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:34.796: INFO: Jan 12 07:44:36.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:36.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:36.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:36.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (252 seconds elapsed) Jan 12 07:44:36.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:36.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:36.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:36.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:36.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:36.796: INFO: Jan 12 07:44:38.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:38.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:38.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:38.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (254 seconds elapsed) Jan 12 07:44:38.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:38.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:38.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:38.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:38.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:38.798: INFO: Jan 12 07:44:40.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:40.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:40.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:40.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (256 seconds elapsed) Jan 12 07:44:40.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:40.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:40.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:40.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:40.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:40.795: INFO: Jan 12 07:44:42.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:42.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:42.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:42.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (258 seconds elapsed) Jan 12 07:44:42.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:42.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:42.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:42.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:42.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:42.795: INFO: Jan 12 07:44:44.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:44.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:44.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:44.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (260 seconds elapsed) Jan 12 07:44:44.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:44.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:44.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:44.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:44.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:44.797: INFO: Jan 12 07:44:46.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:46.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:46.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:46.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (262 seconds elapsed) Jan 12 07:44:46.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:46.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:46.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:46.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:46.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:46.796: INFO: Jan 12 07:44:48.793: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:48.793: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:48.793: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:48.793: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (264 seconds elapsed) Jan 12 07:44:48.793: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:48.793: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:48.793: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:48.793: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:48.793: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:48.793: INFO: Jan 12 07:44:50.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:50.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:50.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:50.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (266 seconds elapsed) Jan 12 07:44:50.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:50.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:50.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:50.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:50.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:50.794: INFO: Jan 12 07:44:52.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:52.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:52.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:52.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (268 seconds elapsed) Jan 12 07:44:52.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:52.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:52.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:52.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:52.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:52.798: INFO: Jan 12 07:44:54.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:54.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:54.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:54.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (270 seconds elapsed) Jan 12 07:44:54.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:54.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:54.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:54.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:54.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:54.796: INFO: Jan 12 07:44:56.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:56.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:56.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:56.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (272 seconds elapsed) Jan 12 07:44:56.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:56.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:56.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:56.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:56.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:56.798: INFO: Jan 12 07:44:58.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:58.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:58.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:44:58.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (274 seconds elapsed) Jan 12 07:44:58.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:44:58.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:44:58.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:58.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:58.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:44:58.795: INFO: Jan 12 07:45:00.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:00.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:00.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:00.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (276 seconds elapsed) Jan 12 07:45:00.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:00.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:00.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:00.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:00.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:00.796: INFO: Jan 12 07:45:02.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:02.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:02.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:02.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (278 seconds elapsed) Jan 12 07:45:02.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:02.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:02.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:02.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:02.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:02.795: INFO: Jan 12 07:45:04.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:04.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:04.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:04.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (280 seconds elapsed) Jan 12 07:45:04.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:04.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:04.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:04.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:04.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:04.795: INFO: Jan 12 07:45:06.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:06.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:06.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:06.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (282 seconds elapsed) Jan 12 07:45:06.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:06.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:06.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:06.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:06.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:06.794: INFO: Jan 12 07:45:08.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:08.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:08.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:08.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (284 seconds elapsed) Jan 12 07:45:08.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:08.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:08.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:08.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:08.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:08.796: INFO: Jan 12 07:45:10.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:10.799: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:10.799: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:10.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (286 seconds elapsed) Jan 12 07:45:10.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:10.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:10.799: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:10.799: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:10.799: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:10.799: INFO: Jan 12 07:45:12.793: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:12.793: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:12.793: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:12.793: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (288 seconds elapsed) Jan 12 07:45:12.793: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:12.793: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:12.793: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:12.793: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:12.793: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:12.793: INFO: Jan 12 07:45:14.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:14.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:14.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:14.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (290 seconds elapsed) Jan 12 07:45:14.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:14.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:14.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:14.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:14.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:14.798: INFO: Jan 12 07:45:16.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:16.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:16.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:16.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (292 seconds elapsed) Jan 12 07:45:16.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:16.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:16.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:16.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:16.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:16.798: INFO: Jan 12 07:45:18.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:18.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:18.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:18.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (294 seconds elapsed) Jan 12 07:45:18.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:18.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:18.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:18.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:18.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:18.794: INFO: Jan 12 07:45:20.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:20.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:20.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:20.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (296 seconds elapsed) Jan 12 07:45:20.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:20.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:20.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:20.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:20.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:20.794: INFO: Jan 12 07:45:22.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:22.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:22.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:22.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (298 seconds elapsed) Jan 12 07:45:22.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:22.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:22.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:22.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:22.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:22.795: INFO: Jan 12 07:45:24.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:24.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:24.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:24.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (300 seconds elapsed) Jan 12 07:45:24.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:24.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:24.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:24.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:24.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:24.796: INFO: Jan 12 07:45:26.801: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:26.801: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:26.801: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:26.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (302 seconds elapsed) Jan 12 07:45:26.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:26.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:26.801: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:26.801: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:26.801: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:26.801: INFO: Jan 12 07:45:28.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:28.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:28.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:28.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (304 seconds elapsed) Jan 12 07:45:28.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:28.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:28.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:28.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:28.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:28.797: INFO: Jan 12 07:45:30.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:30.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:30.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:30.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (306 seconds elapsed) Jan 12 07:45:30.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:30.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:30.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:30.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:30.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:30.795: INFO: Jan 12 07:45:32.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:32.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:32.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:32.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (308 seconds elapsed) Jan 12 07:45:32.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:32.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:32.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:32.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:32.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:32.796: INFO: Jan 12 07:45:34.802: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:34.802: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:34.802: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:34.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (310 seconds elapsed) Jan 12 07:45:34.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:34.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:34.802: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:34.802: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:34.802: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:34.802: INFO: Jan 12 07:45:36.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:36.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:36.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:36.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (312 seconds elapsed) Jan 12 07:45:36.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:36.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:36.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:36.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:36.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:36.796: INFO: Jan 12 07:45:38.802: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:38.802: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:38.802: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:38.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (314 seconds elapsed) Jan 12 07:45:38.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:38.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:38.802: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:38.802: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:38.802: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:38.802: INFO: Jan 12 07:45:40.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:40.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:40.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:40.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (316 seconds elapsed) Jan 12 07:45:40.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:40.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:40.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:40.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:40.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:40.794: INFO: Jan 12 07:45:42.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:42.799: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:42.799: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:42.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (318 seconds elapsed) Jan 12 07:45:42.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:42.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:42.799: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:42.799: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:42.799: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:42.799: INFO: Jan 12 07:45:44.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:44.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:44.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:44.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (320 seconds elapsed) Jan 12 07:45:44.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:44.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:44.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:44.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:44.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:44.795: INFO: Jan 12 07:45:46.793: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:46.793: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:46.793: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:46.793: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (322 seconds elapsed) Jan 12 07:45:46.793: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:46.793: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:46.793: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:46.793: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:46.793: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:46.793: INFO: Jan 12 07:45:48.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:48.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:48.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:48.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (324 seconds elapsed) Jan 12 07:45:48.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:48.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:48.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:48.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:48.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:48.796: INFO: Jan 12 07:45:50.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:50.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:50.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:50.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (326 seconds elapsed) Jan 12 07:45:50.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:50.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:50.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:50.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:50.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:50.800: INFO: Jan 12 07:45:52.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:52.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:52.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:52.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (328 seconds elapsed) Jan 12 07:45:52.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:52.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:52.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:52.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:52.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:52.794: INFO: Jan 12 07:45:54.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:54.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:54.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:54.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (330 seconds elapsed) Jan 12 07:45:54.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:54.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:54.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:54.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:54.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:54.794: INFO: Jan 12 07:45:56.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:56.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:56.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:56.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (332 seconds elapsed) Jan 12 07:45:56.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:56.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:56.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:56.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:56.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:56.795: INFO: Jan 12 07:45:58.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:58.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:58.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:45:58.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (334 seconds elapsed) Jan 12 07:45:58.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:45:58.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:45:58.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:58.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:58.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:45:58.798: INFO: Jan 12 07:46:00.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:00.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:00.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:00.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (336 seconds elapsed) Jan 12 07:46:00.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:00.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:00.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:00.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:00.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:00.800: INFO: Jan 12 07:46:02.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:02.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:02.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:02.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (338 seconds elapsed) Jan 12 07:46:02.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:02.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:02.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:02.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:02.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:02.795: INFO: Jan 12 07:46:04.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:04.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:04.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:04.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (340 seconds elapsed) Jan 12 07:46:04.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:04.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:04.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:04.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:04.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:04.795: INFO: Jan 12 07:46:06.793: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:06.793: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:06.793: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:06.793: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (342 seconds elapsed) Jan 12 07:46:06.793: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:06.793: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:06.793: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:06.793: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:06.793: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:06.793: INFO: Jan 12 07:46:08.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:08.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:08.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:08.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (344 seconds elapsed) Jan 12 07:46:08.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:08.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:08.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:08.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:08.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:08.795: INFO: Jan 12 07:46:10.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:10.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:10.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:10.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (346 seconds elapsed) Jan 12 07:46:10.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:10.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:10.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:10.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:10.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:10.797: INFO: Jan 12 07:46:12.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:12.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:12.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:12.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (348 seconds elapsed) Jan 12 07:46:12.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:12.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:12.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:12.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:12.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:12.794: INFO: Jan 12 07:46:14.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:14.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:14.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:14.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (350 seconds elapsed) Jan 12 07:46:14.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:14.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:14.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:14.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:14.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:14.795: INFO: Jan 12 07:46:16.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:16.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:16.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:16.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (352 seconds elapsed) Jan 12 07:46:16.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:16.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:16.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:16.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:16.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:16.796: INFO: Jan 12 07:46:18.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:18.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:18.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:18.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (354 seconds elapsed) Jan 12 07:46:18.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:18.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:18.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:18.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:18.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:18.796: INFO: Jan 12 07:46:20.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:20.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:20.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:20.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (356 seconds elapsed) Jan 12 07:46:20.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:20.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:20.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:20.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:20.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:20.795: INFO: Jan 12 07:46:22.793: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:22.793: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:22.793: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:22.793: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (358 seconds elapsed) Jan 12 07:46:22.793: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:22.793: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:22.793: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:22.793: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:22.793: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:22.793: INFO: Jan 12 07:46:24.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:24.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:24.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:24.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (360 seconds elapsed) Jan 12 07:46:24.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:24.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:24.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:24.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:24.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:24.797: INFO: Jan 12 07:46:26.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:26.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:26.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:26.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (362 seconds elapsed) Jan 12 07:46:26.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:26.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:26.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:26.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:26.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:26.800: INFO: Jan 12 07:46:28.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:28.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:28.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:28.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (364 seconds elapsed) Jan 12 07:46:28.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:28.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:28.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:28.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:28.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:28.796: INFO: Jan 12 07:46:30.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:30.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:30.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:30.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (366 seconds elapsed) Jan 12 07:46:30.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:30.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:30.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:30.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:30.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:30.800: INFO: Jan 12 07:46:32.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:32.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:32.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:32.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (368 seconds elapsed) Jan 12 07:46:32.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:32.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:32.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:32.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:32.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:32.796: INFO: Jan 12 07:46:34.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:34.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:34.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:34.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (370 seconds elapsed) Jan 12 07:46:34.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:34.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:34.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:34.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:34.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:34.796: INFO: Jan 12 07:46:36.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:36.799: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:36.799: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:36.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (372 seconds elapsed) Jan 12 07:46:36.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:36.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:36.799: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:36.799: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:36.799: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:36.799: INFO: Jan 12 07:46:38.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:38.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:38.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:38.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (374 seconds elapsed) Jan 12 07:46:38.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:38.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:38.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:38.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:38.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:38.796: INFO: Jan 12 07:46:40.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:40.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:40.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:40.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (376 seconds elapsed) Jan 12 07:46:40.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:40.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:40.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:40.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:40.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:40.798: INFO: Jan 12 07:46:42.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:42.799: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:42.799: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:42.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (378 seconds elapsed) Jan 12 07:46:42.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:42.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:42.799: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:42.799: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:42.799: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:42.799: INFO: Jan 12 07:46:44.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:44.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:44.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:44.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (380 seconds elapsed) Jan 12 07:46:44.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:44.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:44.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:44.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:44.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:44.797: INFO: Jan 12 07:46:46.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:46.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:46.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:46.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (382 seconds elapsed) Jan 12 07:46:46.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:46.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:46.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:46.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:46.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:46.797: INFO: Jan 12 07:46:48.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:48.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:48.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:48.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (384 seconds elapsed) Jan 12 07:46:48.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:48.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:48.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:48.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:48.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:48.795: INFO: Jan 12 07:46:50.793: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:50.793: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:50.793: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:50.793: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (386 seconds elapsed) Jan 12 07:46:50.793: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:50.793: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:50.793: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:50.793: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:50.793: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:50.793: INFO: Jan 12 07:46:52.793: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:52.793: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:52.793: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:52.793: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (388 seconds elapsed) Jan 12 07:46:52.793: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:52.793: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:52.793: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:52.793: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:52.793: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:52.793: INFO: Jan 12 07:46:54.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:54.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:54.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:54.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (390 seconds elapsed) Jan 12 07:46:54.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:54.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:54.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:54.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:54.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:54.796: INFO: Jan 12 07:46:56.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:56.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:56.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:56.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (392 seconds elapsed) Jan 12 07:46:56.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:56.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:56.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:56.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:56.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:56.796: INFO: Jan 12 07:46:58.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:58.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:58.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:46:58.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (394 seconds elapsed) Jan 12 07:46:58.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:46:58.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:46:58.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:58.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:58.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:46:58.797: INFO: Jan 12 07:47:00.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:00.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:00.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:00.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (396 seconds elapsed) Jan 12 07:47:00.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:00.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:00.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:00.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:00.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:00.795: INFO: Jan 12 07:47:02.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:02.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:02.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:02.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (398 seconds elapsed) Jan 12 07:47:02.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:02.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:02.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:02.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:02.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:02.795: INFO: Jan 12 07:47:04.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:04.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:04.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:04.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (400 seconds elapsed) Jan 12 07:47:04.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:04.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:04.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:04.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:04.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:04.794: INFO: Jan 12 07:47:06.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:06.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:06.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:06.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (402 seconds elapsed) Jan 12 07:47:06.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:06.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:06.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:06.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:06.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:06.795: INFO: Jan 12 07:47:08.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:08.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:08.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:08.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (404 seconds elapsed) Jan 12 07:47:08.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:08.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:08.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:08.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:08.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:08.795: INFO: Jan 12 07:47:10.793: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:10.793: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:10.793: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:10.793: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (406 seconds elapsed) Jan 12 07:47:10.793: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:10.793: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:10.793: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:10.793: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:10.793: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:10.793: INFO: Jan 12 07:47:12.793: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:12.793: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:12.793: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:12.793: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (408 seconds elapsed) Jan 12 07:47:12.793: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:12.793: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:12.793: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:12.793: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:12.793: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:12.793: INFO: Jan 12 07:47:14.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:14.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:14.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:14.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (410 seconds elapsed) Jan 12 07:47:14.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:14.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:14.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:14.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:14.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:14.794: INFO: Jan 12 07:47:16.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:16.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:16.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:16.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (412 seconds elapsed) Jan 12 07:47:16.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:16.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:16.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:16.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:16.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:16.800: INFO: Jan 12 07:47:18.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:18.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:18.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:18.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (414 seconds elapsed) Jan 12 07:47:18.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:18.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:18.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:18.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:18.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:18.800: INFO: Jan 12 07:47:20.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:20.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:20.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:20.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (416 seconds elapsed) Jan 12 07:47:20.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:20.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:20.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:20.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:20.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:20.795: INFO: Jan 12 07:47:22.793: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:22.793: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:22.793: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:22.793: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (418 seconds elapsed) Jan 12 07:47:22.793: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:22.793: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:22.793: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:22.793: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:22.793: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:22.793: INFO: Jan 12 07:47:24.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:24.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:24.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:24.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (420 seconds elapsed) Jan 12 07:47:24.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:24.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:24.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:24.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:24.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:24.800: INFO: Jan 12 07:47:26.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:26.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:26.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:26.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (422 seconds elapsed) Jan 12 07:47:26.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:26.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:26.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:26.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:26.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:26.798: INFO: Jan 12 07:47:28.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:28.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:28.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:28.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (424 seconds elapsed) Jan 12 07:47:28.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:28.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:28.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:28.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:28.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:28.796: INFO: Jan 12 07:47:30.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:30.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:30.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:30.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (426 seconds elapsed) Jan 12 07:47:30.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:30.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:30.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:30.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:30.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:30.795: INFO: Jan 12 07:47:32.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:32.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:32.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:32.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (428 seconds elapsed) Jan 12 07:47:32.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:32.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:32.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:32.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:32.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:32.796: INFO: Jan 12 07:47:34.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:34.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:34.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:34.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (430 seconds elapsed) Jan 12 07:47:34.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:34.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:34.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:34.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:34.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:34.797: INFO: Jan 12 07:47:36.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:36.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:36.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:36.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (432 seconds elapsed) Jan 12 07:47:36.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:36.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:36.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:36.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:36.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:36.794: INFO: Jan 12 07:47:38.803: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:38.803: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:38.803: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:38.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (434 seconds elapsed) Jan 12 07:47:38.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:38.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:38.803: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:38.803: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:38.803: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:38.803: INFO: Jan 12 07:47:40.796: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:40.796: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:40.796: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:40.796: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (436 seconds elapsed) Jan 12 07:47:40.796: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:40.796: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:40.796: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:40.796: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:40.796: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:40.796: INFO: Jan 12 07:47:42.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:42.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:42.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:42.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (438 seconds elapsed) Jan 12 07:47:42.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:42.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:42.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:42.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:42.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:42.798: INFO: Jan 12 07:47:44.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:44.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:44.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:44.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (440 seconds elapsed) Jan 12 07:47:44.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:44.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:44.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:44.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:44.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:44.795: INFO: Jan 12 07:47:46.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:46.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:46.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:46.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (442 seconds elapsed) Jan 12 07:47:46.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:46.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:46.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:46.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:46.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:46.797: INFO: Jan 12 07:47:48.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:48.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:48.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:48.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (444 seconds elapsed) Jan 12 07:47:48.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:48.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:48.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:48.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:48.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:48.795: INFO: Jan 12 07:47:50.793: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:50.793: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:50.793: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:50.793: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (446 seconds elapsed) Jan 12 07:47:50.793: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:50.793: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:50.793: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:50.793: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:50.793: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:50.793: INFO: Jan 12 07:47:52.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:52.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:52.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:52.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (448 seconds elapsed) Jan 12 07:47:52.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:52.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:52.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:52.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:52.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:52.795: INFO: Jan 12 07:47:54.793: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:54.793: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:54.793: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:54.793: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (450 seconds elapsed) Jan 12 07:47:54.793: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:54.793: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:54.793: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:54.793: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:54.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:54.794: INFO: Jan 12 07:47:56.820: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:56.820: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:56.820: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:56.820: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (452 seconds elapsed) Jan 12 07:47:56.820: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:56.820: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:56.820: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:56.820: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:56.820: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:56.820: INFO: Jan 12 07:47:58.794: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:58.794: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:58.794: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:47:58.794: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (454 seconds elapsed) Jan 12 07:47:58.794: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:47:58.794: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:47:58.794: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:58.794: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:58.794: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:47:58.794: INFO: Jan 12 07:48:00.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:00.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:00.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:00.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (456 seconds elapsed) Jan 12 07:48:00.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:00.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:00.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:00.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:00.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:00.795: INFO: Jan 12 07:48:02.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:02.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:02.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:02.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (458 seconds elapsed) Jan 12 07:48:02.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:02.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:02.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:02.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:02.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:02.795: INFO: Jan 12 07:48:04.801: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:04.801: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:04.801: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:04.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (460 seconds elapsed) Jan 12 07:48:04.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:04.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:04.802: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:04.802: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:04.802: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:04.802: INFO: Jan 12 07:48:06.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:06.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:06.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:06.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (462 seconds elapsed) Jan 12 07:48:06.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:06.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:06.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:06.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:06.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:06.798: INFO: Jan 12 07:48:08.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:08.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:08.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:08.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (464 seconds elapsed) Jan 12 07:48:08.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:08.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:08.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:08.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:08.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:08.800: INFO: Jan 12 07:48:10.811: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:10.811: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:10.811: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:10.811: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (466 seconds elapsed) Jan 12 07:48:10.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:10.811: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:10.811: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:10.811: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:10.811: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:10.811: INFO: Jan 12 07:48:12.802: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:12.802: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:12.802: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:12.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (468 seconds elapsed) Jan 12 07:48:12.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:12.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:12.802: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:12.802: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:12.802: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:12.802: INFO: Jan 12 07:48:14.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:14.799: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:14.799: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:14.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (470 seconds elapsed) Jan 12 07:48:14.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:14.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:14.799: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:14.799: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:14.799: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:14.799: INFO: Jan 12 07:48:16.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:16.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:16.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:16.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (472 seconds elapsed) Jan 12 07:48:16.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:16.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:16.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:16.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:16.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:16.798: INFO: Jan 12 07:48:18.803: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:18.803: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:18.803: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:18.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (474 seconds elapsed) Jan 12 07:48:18.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:18.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:18.803: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:18.803: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:18.803: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:18.803: INFO: Jan 12 07:48:20.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:20.799: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:20.799: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:20.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (476 seconds elapsed) Jan 12 07:48:20.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:20.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:20.799: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:20.799: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:20.799: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:20.799: INFO: Jan 12 07:48:22.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:22.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:22.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:22.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (478 seconds elapsed) Jan 12 07:48:22.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:22.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:22.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:22.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:22.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:22.798: INFO: Jan 12 07:48:24.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:24.799: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:24.799: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:24.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (480 seconds elapsed) Jan 12 07:48:24.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:24.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:24.799: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:24.799: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:24.799: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:24.799: INFO: Jan 12 07:48:26.801: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:26.801: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:26.801: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:26.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (482 seconds elapsed) Jan 12 07:48:26.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:26.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:26.801: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:26.801: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:26.801: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:26.801: INFO: Jan 12 07:48:28.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:28.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:28.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:28.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (484 seconds elapsed) Jan 12 07:48:28.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:28.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:28.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:28.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:28.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:28.800: INFO: Jan 12 07:48:30.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:30.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:30.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:30.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (486 seconds elapsed) Jan 12 07:48:30.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:30.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:30.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:30.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:30.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:30.798: INFO: Jan 12 07:48:32.803: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:32.803: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:32.803: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:32.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (488 seconds elapsed) Jan 12 07:48:32.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:32.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:32.803: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:32.803: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:32.803: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:32.803: INFO: Jan 12 07:48:34.802: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:34.802: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:34.802: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:34.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (490 seconds elapsed) Jan 12 07:48:34.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:34.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:34.802: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:34.802: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:34.802: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:34.802: INFO: Jan 12 07:48:36.805: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:36.805: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:36.805: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:36.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (492 seconds elapsed) Jan 12 07:48:36.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:36.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:36.805: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:36.805: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:36.805: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:36.805: INFO: Jan 12 07:48:38.804: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:38.804: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:38.804: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:38.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (494 seconds elapsed) Jan 12 07:48:38.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:38.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:38.804: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:38.804: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:38.804: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:38.804: INFO: Jan 12 07:48:40.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:40.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:40.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:40.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (496 seconds elapsed) Jan 12 07:48:40.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:40.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:40.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:40.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:40.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:40.800: INFO: Jan 12 07:48:42.804: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:42.804: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:42.804: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:42.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (498 seconds elapsed) Jan 12 07:48:42.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:42.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:42.804: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:42.804: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:42.804: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:42.804: INFO: Jan 12 07:48:44.803: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:44.803: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:44.803: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:44.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (500 seconds elapsed) Jan 12 07:48:44.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:44.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:44.803: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:44.803: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:44.803: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:44.803: INFO: Jan 12 07:48:46.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:46.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:46.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:46.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (502 seconds elapsed) Jan 12 07:48:46.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:46.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:46.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:46.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:46.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:46.800: INFO: Jan 12 07:48:48.810: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:48.810: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:48.810: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:48.810: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (504 seconds elapsed) Jan 12 07:48:48.810: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:48.810: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:48.810: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:48.810: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:48.810: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:48.810: INFO: Jan 12 07:48:50.795: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:50.795: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:50.795: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:50.795: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (506 seconds elapsed) Jan 12 07:48:50.795: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:50.795: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:50.795: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:50.795: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:50.795: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:50.795: INFO: Jan 12 07:48:52.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:52.799: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:52.799: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:52.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (508 seconds elapsed) Jan 12 07:48:52.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:52.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:52.799: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:52.799: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:52.799: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:52.799: INFO: Jan 12 07:48:54.802: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:54.802: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:54.802: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:54.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (510 seconds elapsed) Jan 12 07:48:54.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:54.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:54.802: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:54.802: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:54.802: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:54.802: INFO: Jan 12 07:48:56.807: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:56.807: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:56.807: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:56.807: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (512 seconds elapsed) Jan 12 07:48:56.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:56.807: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:56.807: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:56.807: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:56.807: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:56.807: INFO: Jan 12 07:48:58.806: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:58.806: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:58.806: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:48:58.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (514 seconds elapsed) Jan 12 07:48:58.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:48:58.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:48:58.806: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:58.806: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:58.806: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:48:58.806: INFO: Jan 12 07:49:00.805: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:00.806: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:00.806: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:00.806: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (516 seconds elapsed) Jan 12 07:49:00.806: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:00.806: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:00.806: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:00.806: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:00.806: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:00.806: INFO: Jan 12 07:49:02.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:02.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:02.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:02.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (518 seconds elapsed) Jan 12 07:49:02.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:02.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:02.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:02.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:02.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:02.800: INFO: Jan 12 07:49:04.805: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:04.805: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:04.805: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:04.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (520 seconds elapsed) Jan 12 07:49:04.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:04.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:04.805: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:04.805: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:04.805: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:04.805: INFO: Jan 12 07:49:06.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:06.799: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:06.799: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:06.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (522 seconds elapsed) Jan 12 07:49:06.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:06.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:06.799: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:06.799: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:06.799: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:06.799: INFO: Jan 12 07:49:08.801: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:08.801: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:08.801: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:08.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (524 seconds elapsed) Jan 12 07:49:08.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:08.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:08.801: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:08.801: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:08.801: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:08.801: INFO: Jan 12 07:49:10.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:10.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:10.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:10.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (526 seconds elapsed) Jan 12 07:49:10.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:10.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:10.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:10.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:10.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:10.798: INFO: Jan 12 07:49:12.802: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:12.802: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:12.802: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:12.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (528 seconds elapsed) Jan 12 07:49:12.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:12.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:12.802: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:12.802: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:12.802: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:12.802: INFO: Jan 12 07:49:14.801: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:14.801: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:14.801: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:14.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (530 seconds elapsed) Jan 12 07:49:14.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:14.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:14.801: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:14.801: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:14.801: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:14.801: INFO: Jan 12 07:49:16.802: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:16.802: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:16.802: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:16.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (532 seconds elapsed) Jan 12 07:49:16.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:16.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:16.802: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:16.802: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:16.802: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:16.802: INFO: Jan 12 07:49:18.803: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:18.803: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:18.803: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:18.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (534 seconds elapsed) Jan 12 07:49:18.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:18.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:18.804: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:18.804: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:18.804: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:18.804: INFO: Jan 12 07:49:20.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:20.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:20.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:20.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (536 seconds elapsed) Jan 12 07:49:20.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:20.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:20.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:20.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:20.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:20.798: INFO: Jan 12 07:49:22.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:22.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:22.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:22.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (538 seconds elapsed) Jan 12 07:49:22.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:22.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:22.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:22.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:22.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:22.798: INFO: Jan 12 07:49:24.803: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:24.803: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:24.803: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:24.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (540 seconds elapsed) Jan 12 07:49:24.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:24.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:24.803: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:24.803: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:24.803: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:24.803: INFO: Jan 12 07:49:26.801: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:26.801: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:26.801: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:26.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (542 seconds elapsed) Jan 12 07:49:26.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:26.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:26.801: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:26.801: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:26.801: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:26.801: INFO: Jan 12 07:49:28.811: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:28.811: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:28.811: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:28.811: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (544 seconds elapsed) Jan 12 07:49:28.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:28.811: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:28.811: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:28.811: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:28.811: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:28.811: INFO: Jan 12 07:49:30.802: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:30.802: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:30.802: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:30.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (546 seconds elapsed) Jan 12 07:49:30.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:30.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:30.802: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:30.802: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:30.802: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:30.802: INFO: Jan 12 07:49:32.805: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:32.805: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:32.805: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:32.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (548 seconds elapsed) Jan 12 07:49:32.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:32.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:32.805: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:32.805: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:32.805: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:32.805: INFO: Jan 12 07:49:34.801: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:34.801: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:34.801: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:34.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (550 seconds elapsed) Jan 12 07:49:34.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:34.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:34.801: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:34.801: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:34.801: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:34.801: INFO: Jan 12 07:49:36.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:36.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:36.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:36.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (552 seconds elapsed) Jan 12 07:49:36.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:36.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:36.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:36.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:36.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:36.800: INFO: Jan 12 07:49:38.801: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:38.801: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:38.801: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:38.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (554 seconds elapsed) Jan 12 07:49:38.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:38.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:38.801: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:38.801: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:38.801: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:38.801: INFO: Jan 12 07:49:40.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:40.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:40.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:40.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (556 seconds elapsed) Jan 12 07:49:40.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:40.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:40.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:40.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:40.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:40.800: INFO: Jan 12 07:49:42.802: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:42.802: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:42.802: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:42.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (558 seconds elapsed) Jan 12 07:49:42.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:42.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:42.802: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:42.802: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:42.802: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:42.802: INFO: Jan 12 07:49:44.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:44.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:44.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:44.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (560 seconds elapsed) Jan 12 07:49:44.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:44.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:44.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:44.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:44.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:44.800: INFO: Jan 12 07:49:46.805: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:46.805: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:46.805: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:46.805: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (562 seconds elapsed) Jan 12 07:49:46.805: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:46.805: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:46.805: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:46.805: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:46.805: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:46.805: INFO: Jan 12 07:49:48.807: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:48.807: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:48.807: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:48.807: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (564 seconds elapsed) Jan 12 07:49:48.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:48.807: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:48.807: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:48.807: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:48.807: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:48.807: INFO: Jan 12 07:49:50.802: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:50.802: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:50.802: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:50.802: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (566 seconds elapsed) Jan 12 07:49:50.802: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:50.802: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:50.802: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:50.802: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:50.802: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:50.802: INFO: Jan 12 07:49:52.803: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:52.803: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:52.803: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:52.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (568 seconds elapsed) Jan 12 07:49:52.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:52.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:52.803: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:52.803: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:52.803: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:52.803: INFO: Jan 12 07:49:54.804: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:54.804: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:54.804: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:54.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (570 seconds elapsed) Jan 12 07:49:54.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:54.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:54.804: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:54.804: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:54.804: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:54.804: INFO: Jan 12 07:49:56.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:56.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:56.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:56.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (572 seconds elapsed) Jan 12 07:49:56.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:56.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:56.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:56.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:56.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:56.800: INFO: Jan 12 07:49:58.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:58.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:58.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:49:58.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (574 seconds elapsed) Jan 12 07:49:58.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:49:58.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:49:58.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:58.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:58.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:49:58.798: INFO: Jan 12 07:50:00.800: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:00.800: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:00.800: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:00.800: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (576 seconds elapsed) Jan 12 07:50:00.800: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:50:00.800: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:50:00.800: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:00.800: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:00.800: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:00.800: INFO: Jan 12 07:50:02.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:02.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:02.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:02.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (578 seconds elapsed) Jan 12 07:50:02.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:50:02.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:50:02.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:02.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:02.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:02.798: INFO: Jan 12 07:50:04.804: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:04.804: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:04.804: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:04.804: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (580 seconds elapsed) Jan 12 07:50:04.804: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:50:04.804: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:50:04.804: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:04.804: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:04.804: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:04.804: INFO: Jan 12 07:50:06.801: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:06.801: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:06.801: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:06.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (582 seconds elapsed) Jan 12 07:50:06.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:50:06.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:50:06.801: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:06.801: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:06.801: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:06.801: INFO: Jan 12 07:50:08.803: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:08.803: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:08.803: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:08.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (584 seconds elapsed) Jan 12 07:50:08.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:50:08.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:50:08.803: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:08.803: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:08.803: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:08.803: INFO: Jan 12 07:50:10.797: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:10.797: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:10.797: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:10.797: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (586 seconds elapsed) Jan 12 07:50:10.797: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:50:10.797: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:50:10.797: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:10.797: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:10.797: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:10.797: INFO: Jan 12 07:50:12.799: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:12.799: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:12.799: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:12.799: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (588 seconds elapsed) Jan 12 07:50:12.799: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:50:12.799: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:50:12.799: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:12.799: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:12.799: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:12.799: INFO: Jan 12 07:50:14.803: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:14.803: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:14.803: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:14.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (590 seconds elapsed) Jan 12 07:50:14.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:50:14.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:50:14.803: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:14.803: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:14.803: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:14.803: INFO: Jan 12 07:50:16.798: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:16.798: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:16.798: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:16.798: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (592 seconds elapsed) Jan 12 07:50:16.798: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:50:16.798: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:50:16.798: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:16.798: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:16.798: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:16.798: INFO: Jan 12 07:50:18.811: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:18.811: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:18.811: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:18.811: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (594 seconds elapsed) Jan 12 07:50:18.811: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:50:18.811: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:50:18.811: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:18.811: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:18.811: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:18.811: INFO: Jan 12 07:50:20.807: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:20.807: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:20.807: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:20.807: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (596 seconds elapsed) Jan 12 07:50:20.807: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:50:20.807: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:50:20.807: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:20.807: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:20.807: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:20.807: INFO: Jan 12 07:50:22.803: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:22.803: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:22.803: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:22.803: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (598 seconds elapsed) Jan 12 07:50:22.803: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:50:22.803: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:50:22.803: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:22.803: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:22.803: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:22.803: INFO: Jan 12 07:50:24.801: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:24.801: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:24.801: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:24.801: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Jan 12 07:50:24.801: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:50:24.801: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:50:24.801: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:24.801: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:24.801: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:24.801: INFO: Jan 12 07:50:24.942: INFO: The status of Pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:24.942: INFO: The status of Pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:24.942: INFO: The status of Pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Jan 12 07:50:24.942: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed) Jan 12 07:50:24.942: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Jan 12 07:50:24.942: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:50:24.942: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:24.942: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:24.942: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:24.942: INFO: �[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m01/12/23 07:50:24.942�[0m �[1mSTEP:�[0m Found 98 events. �[38;5;243m01/12/23 07:50:24.998�[0m Jan 12 07:50:24.998: INFO: At 2023-01-12 07:38:00 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-fg0xvh-control-plane-69nqp_a62e05d6-9cb5-416c-a5f4-b93c288acd2a became leader Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:00 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-fg0xvh-control-plane-69nqp_d96fd65b-d346-4147-bec5-a196abadf6a1 became leader Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:05 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-565d847f94 to 2 Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:05 +0000 UTC - event for coredns-565d847f94: {replicaset-controller } SuccessfulCreate: Created pod: coredns-565d847f94-rcm75 Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:05 +0000 UTC - event for coredns-565d847f94: {replicaset-controller } SuccessfulCreate: Created pod: coredns-565d847f94-w52p7 Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:05 +0000 UTC - event for coredns-565d847f94-rcm75: {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. Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:05 +0000 UTC - event for coredns-565d847f94-w52p7: {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. Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:05 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-82gbg Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:05 +0000 UTC - event for kube-proxy-82gbg: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-82gbg to capz-conf-fg0xvh-control-plane-69nqp Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:06 +0000 UTC - event for kube-proxy-82gbg: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.25.6-rc.0.43_b99d1a81caaed8" Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:07 +0000 UTC - event for kube-proxy-82gbg: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Created: Created container kube-proxy Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:07 +0000 UTC - event for kube-proxy-82gbg: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.25.6-rc.0.43_b99d1a81caaed8" in 1.764280123s (1.764300523s including waiting) Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:08 +0000 UTC - event for kube-proxy-82gbg: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Started: Started container kube-proxy Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:18 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-76f7667fbf to 1 Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:18 +0000 UTC - event for metrics-server-76f7667fbf: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-76f7667fbf-whncp Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:18 +0000 UTC - event for metrics-server-76f7667fbf-whncp: {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. Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:20 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-755ff8d7b5 to 1 Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:20 +0000 UTC - event for calico-kube-controllers-755ff8d7b5: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-755ff8d7b5-54ddd Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:20 +0000 UTC - event for calico-kube-controllers-755ff8d7b5-54ddd: {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. Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:20 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-9r5jc Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:20 +0000 UTC - event for calico-node-9r5jc: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-9r5jc to capz-conf-fg0xvh-control-plane-69nqp Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:21 +0000 UTC - event for calico-node-9r5jc: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:28 +0000 UTC - event for calico-node-9r5jc: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 7.723871582s (7.723891682s including waiting) Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:29 +0000 UTC - event for calico-node-9r5jc: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Created: Created container upgrade-ipam Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:29 +0000 UTC - event for calico-node-9r5jc: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Started: Started container upgrade-ipam Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:31 +0000 UTC - event for calico-node-9r5jc: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:31 +0000 UTC - event for calico-node-9r5jc: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Created: Created container install-cni Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:32 +0000 UTC - event for calico-node-9r5jc: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Started: Started container install-cni Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:34 +0000 UTC - event for calico-node-9r5jc: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:43 +0000 UTC - event for calico-kube-controllers-755ff8d7b5-54ddd: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-755ff8d7b5-54ddd to capz-conf-fg0xvh-control-plane-69nqp Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:43 +0000 UTC - event for coredns-565d847f94-rcm75: {kubelet capz-conf-fg0xvh-control-plane-69nqp} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "403c3dbd7bc0dc6850171a6875c1b1d35b9500d4d458d334a276bb2444693c06": 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/ Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:43 +0000 UTC - event for coredns-565d847f94-rcm75: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-565d847f94-rcm75 to capz-conf-fg0xvh-control-plane-69nqp Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:43 +0000 UTC - event for coredns-565d847f94-w52p7: {kubelet capz-conf-fg0xvh-control-plane-69nqp} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "0603d78bcf1b88afeb07ff8a8bc69d62664d3cde67e9d8dff7b576dc54d8f410": 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/ Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:43 +0000 UTC - event for coredns-565d847f94-w52p7: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-565d847f94-w52p7 to capz-conf-fg0xvh-control-plane-69nqp Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:43 +0000 UTC - event for metrics-server-76f7667fbf-whncp: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-76f7667fbf-whncp to capz-conf-fg0xvh-control-plane-69nqp Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:44 +0000 UTC - event for calico-kube-controllers-755ff8d7b5-54ddd: {kubelet capz-conf-fg0xvh-control-plane-69nqp} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "48288187f60f387b5bbd3853a0207799341fb3da5d69a6d29d38edb2f98bd9ac": 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/ Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:44 +0000 UTC - event for calico-node-9r5jc: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Created: Created container calico-node Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:44 +0000 UTC - event for calico-node-9r5jc: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 9.471303812s (9.471361312s including waiting) Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:44 +0000 UTC - event for calico-node-9r5jc: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Started: Started container calico-node Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:44 +0000 UTC - event for metrics-server-76f7667fbf-whncp: {kubelet capz-conf-fg0xvh-control-plane-69nqp} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "5d24cf7bab23dc9faa5303f93d96621ab4ce72257fd574c3810419901f637ca3": 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/ Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:45 +0000 UTC - event for calico-node-9r5jc: {kubelet capz-conf-fg0xvh-control-plane-69nqp} 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 Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:55 +0000 UTC - event for coredns-565d847f94-w52p7: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Unhealthy: Readiness probe failed: Get "http://192.168.22.130:8181/ready": dial tcp 192.168.22.130:8181: connect: connection refused Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:55 +0000 UTC - event for coredns-565d847f94-w52p7: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Started: Started container coredns Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:55 +0000 UTC - event for coredns-565d847f94-w52p7: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Created: Created container coredns Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:55 +0000 UTC - event for coredns-565d847f94-w52p7: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:55 +0000 UTC - event for metrics-server-76f7667fbf-whncp: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:56 +0000 UTC - event for calico-kube-controllers-755ff8d7b5-54ddd: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0" Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:59 +0000 UTC - event for coredns-565d847f94-rcm75: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Created: Created container coredns Jan 12 07:50:24.999: INFO: At 2023-01-12 07:38:59 +0000 UTC - event for coredns-565d847f94-rcm75: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:00 +0000 UTC - event for coredns-565d847f94-rcm75: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Started: Started container coredns Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:00 +0000 UTC - event for coredns-565d847f94-rcm75: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Unhealthy: Readiness probe failed: Get "http://192.168.22.132:8181/ready": dial tcp 192.168.22.132:8181: connect: connection refused Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:01 +0000 UTC - event for metrics-server-76f7667fbf-whncp: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Created: Created container metrics-server Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:01 +0000 UTC - event for metrics-server-76f7667fbf-whncp: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Started: Started container metrics-server Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:01 +0000 UTC - event for metrics-server-76f7667fbf-whncp: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 6.154154069s (6.154341961s including waiting) Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:07 +0000 UTC - event for calico-kube-controllers-755ff8d7b5-54ddd: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Started: Started container calico-kube-controllers Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:07 +0000 UTC - event for calico-kube-controllers-755ff8d7b5-54ddd: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 5.521414097s (10.817457713s including waiting) Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:07 +0000 UTC - event for calico-kube-controllers-755ff8d7b5-54ddd: {kubelet capz-conf-fg0xvh-control-plane-69nqp} Created: Created container calico-kube-controllers Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:16 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-62sbc Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:16 +0000 UTC - event for calico-node-62sbc: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-62sbc to capz-conf-fg0xvh-md-0-fdcn2 Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:16 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-hspvq Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:16 +0000 UTC - event for kube-proxy-hspvq: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-hspvq to capz-conf-fg0xvh-md-0-fdcn2 Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:26 +0000 UTC - event for calico-node-62sbc: {kubelet capz-conf-fg0xvh-md-0-fdcn2} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:26 +0000 UTC - event for kube-proxy-hspvq: {kubelet capz-conf-fg0xvh-md-0-fdcn2} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.25.6-rc.0.43_b99d1a81caaed8" Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:31 +0000 UTC - event for kube-proxy-hspvq: {kubelet capz-conf-fg0xvh-md-0-fdcn2} Started: Started container kube-proxy Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:31 +0000 UTC - event for kube-proxy-hspvq: {kubelet capz-conf-fg0xvh-md-0-fdcn2} Created: Created container kube-proxy Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:31 +0000 UTC - event for kube-proxy-hspvq: {kubelet capz-conf-fg0xvh-md-0-fdcn2} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.25.6-rc.0.43_b99d1a81caaed8" in 4.367179974s (4.367261575s including waiting) Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:38 +0000 UTC - event for calico-node-62sbc: {kubelet capz-conf-fg0xvh-md-0-fdcn2} Started: Started container upgrade-ipam Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:38 +0000 UTC - event for calico-node-62sbc: {kubelet capz-conf-fg0xvh-md-0-fdcn2} Created: Created container upgrade-ipam Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:38 +0000 UTC - event for calico-node-62sbc: {kubelet capz-conf-fg0xvh-md-0-fdcn2} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 7.245179726s (11.59573383s including waiting) Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:40 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-v4s4q Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:40 +0000 UTC - event for calico-node-v4s4q: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-v4s4q to capz-conf-fg0xvh-md-0-ssgl2 Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:40 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-fkzlr Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:40 +0000 UTC - event for kube-proxy-fkzlr: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-fkzlr to capz-conf-fg0xvh-md-0-ssgl2 Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:41 +0000 UTC - event for calico-node-62sbc: {kubelet capz-conf-fg0xvh-md-0-fdcn2} Created: Created container install-cni Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:41 +0000 UTC - event for calico-node-62sbc: {kubelet capz-conf-fg0xvh-md-0-fdcn2} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:41 +0000 UTC - event for calico-node-62sbc: {kubelet capz-conf-fg0xvh-md-0-fdcn2} Started: Started container install-cni Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:44 +0000 UTC - event for calico-node-62sbc: {kubelet capz-conf-fg0xvh-md-0-fdcn2} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:50 +0000 UTC - event for calico-node-v4s4q: {kubelet capz-conf-fg0xvh-md-0-ssgl2} Pulling: Pulling image "docker.io/calico/cni:v3.23.0" Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:50 +0000 UTC - event for kube-proxy-fkzlr: {kubelet capz-conf-fg0xvh-md-0-ssgl2} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.25.6-rc.0.43_b99d1a81caaed8" Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:51 +0000 UTC - event for calico-node-62sbc: {kubelet capz-conf-fg0xvh-md-0-fdcn2} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 6.813529035s (6.813534435s including waiting) Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:51 +0000 UTC - event for calico-node-62sbc: {kubelet capz-conf-fg0xvh-md-0-fdcn2} Created: Created container calico-node Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:51 +0000 UTC - event for calico-node-62sbc: {kubelet capz-conf-fg0xvh-md-0-fdcn2} Started: Started container calico-node Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:52 +0000 UTC - event for calico-node-62sbc: {kubelet capz-conf-fg0xvh-md-0-fdcn2} 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 Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:54 +0000 UTC - event for kube-proxy-fkzlr: {kubelet capz-conf-fg0xvh-md-0-ssgl2} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.25.6-rc.0.43_b99d1a81caaed8" in 4.335974373s (4.336123882s including waiting) Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:54 +0000 UTC - event for kube-proxy-fkzlr: {kubelet capz-conf-fg0xvh-md-0-ssgl2} Created: Created container kube-proxy Jan 12 07:50:24.999: INFO: At 2023-01-12 07:39:55 +0000 UTC - event for kube-proxy-fkzlr: {kubelet capz-conf-fg0xvh-md-0-ssgl2} Started: Started container kube-proxy Jan 12 07:50:24.999: INFO: At 2023-01-12 07:40:01 +0000 UTC - event for calico-node-v4s4q: {kubelet capz-conf-fg0xvh-md-0-ssgl2} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 6.626681507s (10.953330948s including waiting) Jan 12 07:50:24.999: INFO: At 2023-01-12 07:40:01 +0000 UTC - event for calico-node-v4s4q: {kubelet capz-conf-fg0xvh-md-0-ssgl2} Created: Created container upgrade-ipam Jan 12 07:50:24.999: INFO: At 2023-01-12 07:40:01 +0000 UTC - event for calico-node-v4s4q: {kubelet capz-conf-fg0xvh-md-0-ssgl2} Started: Started container upgrade-ipam Jan 12 07:50:24.999: INFO: At 2023-01-12 07:40:04 +0000 UTC - event for calico-node-v4s4q: {kubelet capz-conf-fg0xvh-md-0-ssgl2} Created: Created container install-cni Jan 12 07:50:24.999: INFO: At 2023-01-12 07:40:04 +0000 UTC - event for calico-node-v4s4q: {kubelet capz-conf-fg0xvh-md-0-ssgl2} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine Jan 12 07:50:24.999: INFO: At 2023-01-12 07:40:04 +0000 UTC - event for calico-node-v4s4q: {kubelet capz-conf-fg0xvh-md-0-ssgl2} Started: Started container install-cni Jan 12 07:50:24.999: INFO: At 2023-01-12 07:40:07 +0000 UTC - event for calico-node-v4s4q: {kubelet capz-conf-fg0xvh-md-0-ssgl2} Pulling: Pulling image "docker.io/calico/node:v3.23.0" Jan 12 07:50:24.999: INFO: At 2023-01-12 07:40:14 +0000 UTC - event for calico-node-v4s4q: {kubelet capz-conf-fg0xvh-md-0-ssgl2} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 7.058017555s (7.058023356s including waiting) Jan 12 07:50:24.999: INFO: At 2023-01-12 07:40:14 +0000 UTC - event for calico-node-v4s4q: {kubelet capz-conf-fg0xvh-md-0-ssgl2} Created: Created container calico-node Jan 12 07:50:24.999: INFO: At 2023-01-12 07:40:14 +0000 UTC - event for calico-node-v4s4q: {kubelet capz-conf-fg0xvh-md-0-ssgl2} Started: Started container calico-node Jan 12 07:50:24.999: INFO: At 2023-01-12 07:40:15 +0000 UTC - event for calico-node-v4s4q: {kubelet capz-conf-fg0xvh-md-0-ssgl2} 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 Jan 12 07:50:24.999: INFO: At 2023-01-12 07:40:16 +0000 UTC - event for calico-node-v4s4q: {kubelet capz-conf-fg0xvh-md-0-ssgl2} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503 Jan 12 07:50:25.060: INFO: POD NODE PHASE GRACE CONDITIONS Jan 12 07:50:25.060: INFO: calico-kube-controllers-755ff8d7b5-54ddd capz-conf-fg0xvh-control-plane-69nqp Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:43 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:08 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:08 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:43 +0000 UTC }] Jan 12 07:50:25.060: INFO: calico-node-62sbc capz-conf-fg0xvh-md-0-fdcn2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:44 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:53 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:53 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:16 +0000 UTC }] Jan 12 07:50:25.060: INFO: calico-node-9r5jc capz-conf-fg0xvh-control-plane-69nqp Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:34 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:51 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:51 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:20 +0000 UTC }] Jan 12 07:50:25.060: INFO: calico-node-v4s4q capz-conf-fg0xvh-md-0-ssgl2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:40:07 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:40:17 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:40:17 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:40 +0000 UTC }] Jan 12 07:50:25.060: INFO: coredns-565d847f94-rcm75 capz-conf-fg0xvh-control-plane-69nqp Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:43 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:13 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:13 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:43 +0000 UTC }] Jan 12 07:50:25.060: INFO: coredns-565d847f94-w52p7 capz-conf-fg0xvh-control-plane-69nqp Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:43 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:13 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:13 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:43 +0000 UTC }] Jan 12 07:50:25.060: INFO: etcd-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:02 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:09 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:09 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:02 +0000 UTC }] Jan 12 07:50:25.060: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:25.060: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:25.060: INFO: kube-proxy-82gbg capz-conf-fg0xvh-control-plane-69nqp Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:05 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:08 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:08 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:05 +0000 UTC }] Jan 12 07:50:25.060: INFO: kube-proxy-fkzlr capz-conf-fg0xvh-md-0-ssgl2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:47 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:55 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:55 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:40 +0000 UTC }] Jan 12 07:50:25.060: INFO: kube-proxy-hspvq capz-conf-fg0xvh-md-0-fdcn2 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:22 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:31 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:31 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:16 +0000 UTC }] Jan 12 07:50:25.060: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Jan 12 07:50:25.060: INFO: metrics-server-76f7667fbf-whncp capz-conf-fg0xvh-control-plane-69nqp Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:43 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:23 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:39:23 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-12 07:38:43 +0000 UTC }] Jan 12 07:50:25.060: INFO: Jan 12 07:50:25.342: INFO: Logging node info for node capz-conf-fg0xvh-control-plane-69nqp Jan 12 07:50:25.378: INFO: Node Info: &Node{ObjectMeta:{capz-conf-fg0xvh-control-plane-69nqp 61b12fda-ba3b-46bb-8d0a-e9dbaf1503c0 1703 0 2023-01-12 07:37:59 +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-2 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-fg0xvh-control-plane-69nqp 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-2] map[cluster.x-k8s.io/cluster-name:capz-conf-fg0xvh cluster.x-k8s.io/cluster-namespace:capz-conf-fg0xvh cluster.x-k8s.io/machine:capz-conf-fg0xvh-control-plane-2rsz7 cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-fg0xvh-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.22.128 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-12 07:37:59 +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 2023-01-12 07:38:00 +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 2023-01-12 07:38:17 +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 2023-01-12 07:38:43 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2023-01-12 07:38:44 +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 2023-01-12 07:49:46 +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-fg0xvh/providers/Microsoft.Compute/virtualMachines/capz-conf-fg0xvh-control-plane-69nqp,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: {{8344743936 0} {<nil>} 8149164Ki 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: {{8239886336 0} {<nil>} 8046764Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-12 07:38:44 +0000 UTC,LastTransitionTime:2023-01-12 07:38:44 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-12 07:49:46 +0000 UTC,LastTransitionTime:2023-01-12 07:37:36 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-12 07:49:46 +0000 UTC,LastTransitionTime:2023-01-12 07:37:36 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-12 07:49:46 +0000 UTC,LastTransitionTime:2023-01-12 07:37:36 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-12 07:49:46 +0000 UTC,LastTransitionTime:2023-01-12 07:38:42 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-fg0xvh-control-plane-69nqp,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:054871063d8b44f388f965c668f6b53e,SystemUUID:b3297db4-33af-1042-820e-f8ffb9a88a45,BootID:0297f697-5c16-482f-8250-145d42dff528,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.25.6-rc.0.43+b99d1a81caaed8,KubeProxyVersion:v1.25.6-rc.0.43+b99d1a81caaed8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[docker.io/calico/cni@sha256:914823d144204288f881e49b93b6852febfe669074cd4e2a782860981615f521 docker.io/calico/cni:v3.23.0],SizeBytes:110494683,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[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:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-apiserver@sha256:d71cd06d1752327bb381cbed883aeb4f920be3dff69c3a8a007f4dd23690a790 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.25.6-rc.0.41_7240b34c44cef4],SizeBytes:34253856,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-controller-manager@sha256:3e0c7002371f24a0df0263307bd641084cfe70aaafd56ae4e875338c32aeb119 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.25.6-rc.0.41_7240b34c44cef4],SizeBytes:31267058,},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:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:bf542c451fd662c40468b1b34448d24b81822058a5eee0bda8a4f6fb45541cf7 gcr.io/k8s-staging-ci-images/kube-proxy:v1.25.6-rc.0.41_7240b34c44cef4],SizeBytes:20276078,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:f3c58b77383fe6a1a6c0c50763723b46856cc5e00adb95db54b49a3228dea977 capzci.azurecr.io/kube-proxy:v1.25.6-rc.0.43_b99d1a81caaed8],SizeBytes:20274386,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-scheduler@sha256:6fd855f772bfc750383d786a18b61f3ca0817d88d2b143b8e667ea6a77e71ddd gcr.io/k8s-staging-ci-images/kube-scheduler:v1.25.6-rc.0.41_7240b34c44cef4],SizeBytes:15800036,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 12 07:50:25.379: INFO: Logging kubelet events for node capz-conf-fg0xvh-control-plane-69nqp Jan 12 07:50:25.509: INFO: Logging pods the kubelet thinks is on node capz-conf-fg0xvh-control-plane-69nqp Jan 12 07:50:25.717: INFO: kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp started at <nil> (0+0 container statuses recorded) Jan 12 07:50:25.717: INFO: kube-proxy-82gbg started at 2023-01-12 07:38:05 +0000 UTC (0+1 container statuses recorded) Jan 12 07:50:25.717: INFO: Container kube-proxy ready: true, restart count 0 Jan 12 07:50:25.717: INFO: calico-node-9r5jc started at 2023-01-12 07:38:20 +0000 UTC (2+1 container statuses recorded) Jan 12 07:50:25.717: INFO: Init container upgrade-ipam ready: true, restart count 0 Jan 12 07:50:25.717: INFO: Init container install-cni ready: true, restart count 0 Jan 12 07:50:25.717: INFO: Container calico-node ready: true, restart count 0 Jan 12 07:50:25.717: INFO: coredns-565d847f94-rcm75 started at 2023-01-12 07:38:43 +0000 UTC (0+1 container statuses recorded) Jan 12 07:50:25.717: INFO: Container coredns ready: true, restart count 0 Jan 12 07:50:25.717: INFO: coredns-565d847f94-w52p7 started at 2023-01-12 07:38:43 +0000 UTC (0+1 container statuses recorded) Jan 12 07:50:25.717: INFO: Container coredns ready: true, restart count 0 Jan 12 07:50:25.717: INFO: kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp started at <nil> (0+0 container statuses recorded) Jan 12 07:50:25.717: INFO: kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp started at <nil> (0+0 container statuses recorded) Jan 12 07:50:25.717: INFO: etcd-capz-conf-fg0xvh-control-plane-69nqp started at 2023-01-12 07:38:02 +0000 UTC (0+1 container statuses recorded) Jan 12 07:50:25.717: INFO: Container etcd ready: true, restart count 0 Jan 12 07:50:25.717: INFO: metrics-server-76f7667fbf-whncp started at 2023-01-12 07:38:43 +0000 UTC (0+1 container statuses recorded) Jan 12 07:50:25.717: INFO: Container metrics-server ready: true, restart count 0 Jan 12 07:50:25.717: INFO: calico-kube-controllers-755ff8d7b5-54ddd started at 2023-01-12 07:38:43 +0000 UTC (0+1 container statuses recorded) Jan 12 07:50:25.717: INFO: Container calico-kube-controllers ready: true, restart count 0 Jan 12 07:50:26.358: INFO: Latency metrics for node capz-conf-fg0xvh-control-plane-69nqp Jan 12 07:50:26.358: INFO: Logging node info for node capz-conf-fg0xvh-md-0-fdcn2 Jan 12 07:50:26.504: INFO: Node Info: &Node{ObjectMeta:{capz-conf-fg0xvh-md-0-fdcn2 e968712c-56c6-4ebb-8dc8-971199b80b5e 1750 0 2023-01-12 07:39:16 +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:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-fg0xvh-md-0-fdcn2 kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-fg0xvh cluster.x-k8s.io/cluster-namespace:capz-conf-fg0xvh cluster.x-k8s.io/machine:capz-conf-fg0xvh-md-0-7db48f656f-4rzj4 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-fg0xvh-md-0-7db48f656f kubeadm.alpha.kubernetes.io/cri-socket:unix:///var/run/containerd/containerd.sock node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.1.0.4/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.189.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-12 07:39:16 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet Update v1 2023-01-12 07:39:16 +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":{}}} } {manager Update v1 2023-01-12 07:39:28 +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 2023-01-12 07:39:51 +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} {kube-controller-manager Update v1 2023-01-12 07:39:57 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {kubelet Update v1 2023-01-12 07:50:19 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-fg0xvh/providers/Microsoft.Compute/virtualMachines/capz-conf-fg0xvh-md-0-fdcn2,Unschedulable:false,Taints:[]Taint{},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: {{8344743936 0} {<nil>} 8149164Ki 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: {{8239886336 0} {<nil>} 8046764Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-12 07:39:51 +0000 UTC,LastTransitionTime:2023-01-12 07:39:51 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-12 07:50:18 +0000 UTC,LastTransitionTime:2023-01-12 07:39:16 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-12 07:50:18 +0000 UTC,LastTransitionTime:2023-01-12 07:39:16 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-12 07:50:18 +0000 UTC,LastTransitionTime:2023-01-12 07:39:16 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-12 07:50:18 +0000 UTC,LastTransitionTime:2023-01-12 07:39:57 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-fg0xvh-md-0-fdcn2,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:c16b3f61a2c24112be6cc215df11fea0,SystemUUID:4155b3a5-9485-2b40-bcc8-ff73c0c01c8e,BootID:d39d6af2-63e5-410f-81cf-a934ddef8992,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.25.6-rc.0.43+b99d1a81caaed8,KubeProxyVersion:v1.25.6-rc.0.43+b99d1a81caaed8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[docker.io/calico/cni@sha256:914823d144204288f881e49b93b6852febfe669074cd4e2a782860981615f521 docker.io/calico/cni:v3.23.0],SizeBytes:110494683,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[docker.io/calico/node@sha256:4763820ecb4d8e82483a2ffabfec7fcded9603318692df210a778d223a4d7474 docker.io/calico/node:v3.23.0],SizeBytes:71573794,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:f3c58b77383fe6a1a6c0c50763723b46856cc5e00adb95db54b49a3228dea977 capzci.azurecr.io/kube-proxy:v1.25.6-rc.0.43_b99d1a81caaed8],SizeBytes:20274386,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 12 07:50:26.505: INFO: Logging kubelet events for node capz-conf-fg0xvh-md-0-fdcn2 Jan 12 07:50:26.706: INFO: Logging pods the kubelet thinks is on node capz-conf-fg0xvh-md-0-fdcn2 Jan 12 07:50:26.911: INFO: kube-proxy-hspvq started at 2023-01-12 07:39:22 +0000 UTC (0+1 container statuses recorded) Jan 12 07:50:26.911: INFO: Container kube-proxy ready: true, restart count 0 Jan 12 07:50:26.911: INFO: calico-node-62sbc started at 2023-01-12 07:39:22 +0000 UTC (2+1 container statuses recorded) Jan 12 07:50:26.911: INFO: Init container upgrade-ipam ready: true, restart count 0 Jan 12 07:50:26.911: INFO: Init container install-cni ready: true, restart count 0 Jan 12 07:50:26.911: INFO: Container calico-node ready: true, restart count 0 Jan 12 07:50:27.534: INFO: Latency metrics for node capz-conf-fg0xvh-md-0-fdcn2 Jan 12 07:50:27.534: INFO: Logging node info for node capz-conf-fg0xvh-md-0-ssgl2 Jan 12 07:50:27.708: INFO: Node Info: &Node{ObjectMeta:{capz-conf-fg0xvh-md-0-ssgl2 521303b8-a34b-4067-91d4-00ab0d6ba17b 1355 0 2023-01-12 07:39:40 +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:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-fg0xvh-md-0-ssgl2 kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-fg0xvh cluster.x-k8s.io/cluster-namespace:capz-conf-fg0xvh cluster.x-k8s.io/machine:capz-conf-fg0xvh-md-0-7db48f656f-kjhvg cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-fg0xvh-md-0-7db48f656f kubeadm.alpha.kubernetes.io/cri-socket:unix:///var/run/containerd/containerd.sock node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.1.0.5/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.118.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-12 07:39:40 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet Update v1 2023-01-12 07:39:40 +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":{}}} } {manager Update v1 2023-01-12 07:39:48 +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 2023-01-12 07:40:10 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {Go-http-client Update v1 2023-01-12 07:40:15 +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 2023-01-12 07:45:36 +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-fg0xvh/providers/Microsoft.Compute/virtualMachines/capz-conf-fg0xvh-md-0-ssgl2,Unschedulable:false,Taints:[]Taint{},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: {{8344743936 0} {<nil>} 8149164Ki 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: {{8239886336 0} {<nil>} 8046764Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-12 07:40:14 +0000 UTC,LastTransitionTime:2023-01-12 07:40:14 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-12 07:45:36 +0000 UTC,LastTransitionTime:2023-01-12 07:39:39 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-12 07:45:36 +0000 UTC,LastTransitionTime:2023-01-12 07:39:39 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-12 07:45:36 +0000 UTC,LastTransitionTime:2023-01-12 07:39:39 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-12 07:45:36 +0000 UTC,LastTransitionTime:2023-01-12 07:40:10 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-fg0xvh-md-0-ssgl2,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:7c89eeadd74743aeb06954b4989a7cd4,SystemUUID:cc002189-b8c7-d64e-9942-6399c773f699,BootID:20e0aa97-5ae3-4f11-8cae-a2d64752438c,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.25.6-rc.0.43+b99d1a81caaed8,KubeProxyVersion:v1.25.6-rc.0.43+b99d1a81caaed8,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[docker.io/calico/cni@sha256:914823d144204288f881e49b93b6852febfe669074cd4e2a782860981615f521 docker.io/calico/cni:v3.23.0],SizeBytes:110494683,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[docker.io/calico/node@sha256:4763820ecb4d8e82483a2ffabfec7fcded9603318692df210a778d223a4d7474 docker.io/calico/node:v3.23.0],SizeBytes:71573794,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:d230a0b88a3daf14e4cce03b906b992c8153f37da878677f434b1af8c4e8cc75 registry.k8s.io/kube-apiserver:v1.26.0],SizeBytes:35317868,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:1e9bbe429e4e2b2ad32681c91deb98a334f1bf4135137df5f84f9d03689060fe registry.k8s.io/kube-proxy:v1.26.0],SizeBytes:21536465,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:f3c58b77383fe6a1a6c0c50763723b46856cc5e00adb95db54b49a3228dea977 capzci.azurecr.io/kube-proxy:v1.25.6-rc.0.43_b99d1a81caaed8],SizeBytes:20274386,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:34a142549f94312b41d4a6cd98e7fddabff484767a199333acb7503bf46d7410 registry.k8s.io/kube-scheduler:v1.26.0],SizeBytes:17484038,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},} Jan 12 07:50:27.708: INFO: Logging kubelet events for node capz-conf-fg0xvh-md-0-ssgl2 Jan 12 07:50:27.906: INFO: Logging pods the kubelet thinks is on node capz-conf-fg0xvh-md-0-ssgl2 Jan 12 07:50:28.111: INFO: calico-node-v4s4q started at 2023-01-12 07:39:47 +0000 UTC (2+1 container statuses recorded) Jan 12 07:50:28.111: INFO: Init container upgrade-ipam ready: true, restart count 0 Jan 12 07:50:28.111: INFO: Init container install-cni ready: true, restart count 0 Jan 12 07:50:28.111: INFO: Container calico-node ready: true, restart count 0 Jan 12 07:50:28.111: INFO: kube-proxy-fkzlr started at 2023-01-12 07:39:47 +0000 UTC (0+1 container statuses recorded) Jan 12 07:50:28.111: INFO: Container kube-proxy ready: true, restart count 0 Jan 12 07:50:28.742: INFO: Latency metrics for node capz-conf-fg0xvh-md-0-ssgl2 Jan 12 07:50:28.932: INFO: Running kubectl logs on non-ready containers in kube-system Jan 12 07:50:29.307: INFO: Failed to get logs of pod kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp) Jan 12 07:50:29.307: INFO: Logs of kube-system/kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp:kube-apiserver on node capz-conf-fg0xvh-control-plane-69nqp Jan 12 07:50:29.307: INFO: : STARTLOG ENDLOG for container kube-system:kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp:kube-apiserver Jan 12 07:50:29.705: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp) Jan 12 07:50:29.705: INFO: Logs of kube-system/kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp:kube-controller-manager on node capz-conf-fg0xvh-control-plane-69nqp Jan 12 07:50:29.705: INFO: : STARTLOG ENDLOG for container kube-system:kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp:kube-controller-manager Jan 12 07:50:30.106: INFO: Failed to get logs of pod kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp) Jan 12 07:50:30.106: INFO: Logs of kube-system/kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp:kube-scheduler on node capz-conf-fg0xvh-control-plane-69nqp Jan 12 07:50:30.106: INFO: : STARTLOG ENDLOG for container kube-system:kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp:kube-scheduler Jan 12 07:50:30.106: FAIL: Error waiting for all pods to be running and ready: 3 / 14 pods in namespace kube-system are NOT in RUNNING and READY state in 10m0s POD NODE PHASE GRACE CONDITIONS kube-apiserver-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] kube-controller-manager-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] kube-scheduler-capz-conf-fg0xvh-control-plane-69nqp capz-conf-fg0xvh-control-plane-69nqp Pending [] Full Stack Trace k8s.io/kubernetes/test/e2e.glob..func1() test/e2e/e2e.go:80 +0x8f
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:76
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:76
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]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
Kubernetes e2e suite [SynchronizedAfterSuite]
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