pull-kubernetes-e2e-capz-conformance #1615024245685882880 Results

Test Failures

capz-e2e [It] Conformance Tests conformance-tests 23m59s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sConformance\sTests\sconformance\-tests$'

[FAILED] Unexpected error:
    <*errors.withStack | 0xc0023ad668>: {
        error: <*errors.withMessage | 0xc0010b44c0>{
            cause: <*errors.errorString | 0xc00102a930>{
                s: "error container run failed with exit code 1",
            },
            msg: "Unable to run conformance tests",
        },
        stack: [0x3143419, 0x353bb67, 0x18e639b, 0x18f9e98, 0x147c741],
    }
    Unable to run conformance tests: error container run failed with exit code 1
occurred
In [It] at: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:238 @ 01/16/23 17:24:01.502

				> Enter [BeforeEach] Conformance Tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:56 @ 01/16/23 17:06:40.263
INFO: Cluster name is capz-conf-vmxw18
STEP: Creating namespace "capz-conf-vmxw18" for hosting the cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:88 @ 01/16/23 17:06:40.263
Jan 16 17:06:40.263: INFO: starting to create namespace for hosting the "capz-conf-vmxw18" test spec
INFO: Creating namespace capz-conf-vmxw18
INFO: Creating event watcher for namespace "capz-conf-vmxw18"
< Exit [BeforeEach] Conformance Tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:56 @ 01/16/23 17:06:40.344 (81ms)
> Enter [It] conformance-tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100 @ 01/16/23 17:06:40.344
conformance-tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:102 @ 01/16/23 17:06:40.344
  conformance-tests
  Name                        | N | Min        | Median     | Mean       | StdDev | Max       
  ============================================================================================
  cluster creation [duration] | 1 | 6m39.8105s | 6m39.8105s | 6m39.8105s | 0s     | 6m39.8105s
INFO: Creating the workload cluster with name "capz-conf-vmxw18" using the "conformance-presubmit-artifacts" template (Kubernetes v1.27.0-alpha.0.999+ed8cad1e80d096, 1 control-plane machines, 2 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster capz-conf-vmxw18 --infrastructure (default) --kubernetes-version v1.27.0-alpha.0.999+ed8cad1e80d096 --control-plane-machine-count 1 --worker-machine-count 2 --flavor conformance-presubmit-artifacts
INFO: Applying the cluster template yaml to the cluster
INFO: Waiting for the cluster infrastructure to be provisioned
STEP: Waiting for cluster to enter the provisioned phase - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/cluster_helpers.go:134 @ 01/16/23 17:06:46.512
INFO: Waiting for control plane to be initialized
STEP: Installing Calico CNI via helm - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:51 @ 01/16/23 17:08:36.639
STEP: Configuring calico CNI helm chart for IPv4 configuration - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:131 @ 01/16/23 17:08:36.64
Jan 16 17:10:36.849: INFO: getting history for release projectcalico
Jan 16 17:10:36.878: INFO: Release projectcalico does not exist, installing it
Jan 16 17:10:37.956: INFO: creating 1 resource(s)
Jan 16 17:10:38.000: INFO: creating 1 resource(s)
Jan 16 17:10:38.046: INFO: creating 1 resource(s)
Jan 16 17:10:38.099: INFO: creating 1 resource(s)
Jan 16 17:10:38.164: INFO: creating 1 resource(s)
Jan 16 17:10:38.216: INFO: creating 1 resource(s)
Jan 16 17:10:38.305: INFO: creating 1 resource(s)
Jan 16 17:10:38.376: INFO: creating 1 resource(s)
Jan 16 17:10:38.414: INFO: creating 1 resource(s)
Jan 16 17:10:38.456: INFO: creating 1 resource(s)
Jan 16 17:10:38.496: INFO: creating 1 resource(s)
Jan 16 17:10:38.537: INFO: creating 1 resource(s)
Jan 16 17:10:38.576: INFO: creating 1 resource(s)
Jan 16 17:10:38.619: INFO: creating 1 resource(s)
Jan 16 17:10:38.658: INFO: creating 1 resource(s)
Jan 16 17:10:38.720: INFO: creating 1 resource(s)
Jan 16 17:10:38.778: INFO: creating 1 resource(s)
Jan 16 17:10:38.820: INFO: creating 1 resource(s)
Jan 16 17:10:38.880: INFO: creating 1 resource(s)
Jan 16 17:10:38.987: INFO: creating 1 resource(s)
Jan 16 17:10:39.240: INFO: creating 1 resource(s)
Jan 16 17:10:39.297: INFO: Clearing discovery cache
Jan 16 17:10:39.297: INFO: beginning wait for 21 resources with timeout of 1m0s
Jan 16 17:10:41.598: INFO: creating 1 resource(s)
Jan 16 17:10:42.021: INFO: creating 6 resource(s)
Jan 16 17:10:42.518: INFO: Install complete
STEP: Waiting for Ready tigera-operator deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:60 @ 01/16/23 17:10:42.748
STEP: waiting for deployment tigera-operator/tigera-operator to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:88 @ 01/16/23 17:10:42.862
Jan 16 17:10:42.863: INFO: starting to wait for deployment to become available
Jan 16 17:10:52.921: INFO: Deployment tigera-operator/tigera-operator is now available, took 10.058258712s
STEP: Waiting for Ready calico-system deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:74 @ 01/16/23 17:10:53.465
STEP: waiting for deployment calico-system/calico-kube-controllers to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:88 @ 01/16/23 17:10:53.602
Jan 16 17:10:53.602: INFO: starting to wait for deployment to become available
Jan 16 17:11:54.378: INFO: Deployment calico-system/calico-kube-controllers is now available, took 1m0.775770711s
STEP: waiting for deployment calico-system/calico-typha to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:88 @ 01/16/23 17:11:54.631
Jan 16 17:11:54.631: INFO: starting to wait for deployment to become available
Jan 16 17:11:54.659: INFO: Deployment calico-system/calico-typha is now available, took 27.943497ms
STEP: Waiting for Ready calico-apiserver deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:79 @ 01/16/23 17:11:54.66
STEP: waiting for deployment calico-apiserver/calico-apiserver to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:88 @ 01/16/23 17:11:54.869
Jan 16 17:11:54.869: INFO: starting to wait for deployment to become available
Jan 16 17:12:04.925: INFO: Deployment calico-apiserver/calico-apiserver is now available, took 10.056721485s
STEP: Waiting for Ready calico-node daemonset pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:84 @ 01/16/23 17:12:04.925
STEP: waiting for daemonset calico-system/calico-node to be complete - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:88 @ 01/16/23 17:12:05.294
Jan 16 17:12:05.294: INFO: waiting for daemonset calico-system/calico-node to be complete
Jan 16 17:12:05.326: INFO: 1 daemonset calico-system/calico-node pods are running, took 32.15062ms
STEP: Waiting for Ready calico windows pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:91 @ 01/16/23 17:12:05.326
STEP: waiting for daemonset calico-system/calico-node-windows to be complete - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:88 @ 01/16/23 17:12:05.528
Jan 16 17:12:05.528: INFO: waiting for daemonset calico-system/calico-node-windows to be complete
Jan 16 17:12:05.561: INFO: 0 daemonset calico-system/calico-node-windows pods are running, took 32.853285ms
STEP: Waiting for Ready calico windows pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:97 @ 01/16/23 17:12:05.561
STEP: waiting for daemonset kube-system/kube-proxy-windows to be complete - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:88 @ 01/16/23 17:12:05.766
Jan 16 17:12:05.766: INFO: waiting for daemonset kube-system/kube-proxy-windows to be complete
Jan 16 17:12:05.793: INFO: 0 daemonset kube-system/kube-proxy-windows pods are running, took 27.57867ms
INFO: Waiting for the first control plane machine managed by capz-conf-vmxw18/capz-conf-vmxw18-control-plane to be provisioned
STEP: Waiting for one control plane node to exist - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/controlplane_helpers.go:133 @ 01/16/23 17:12:05.815
STEP: Installing azure-disk CSI driver components via helm - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cloud-provider-azure.go:71 @ 01/16/23 17:12:05.821
Jan 16 17:12:05.868: INFO: getting history for release azuredisk-csi-driver-oot
Jan 16 17:12:05.897: INFO: Release azuredisk-csi-driver-oot does not exist, installing it
Jan 16 17:12:08.481: INFO: creating 1 resource(s)
Jan 16 17:12:08.600: INFO: creating 18 resource(s)
Jan 16 17:12:08.895: INFO: Install complete
STEP: Waiting for Ready csi-azuredisk-controller deployment pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cloud-provider-azure.go:81 @ 01/16/23 17:12:08.913
STEP: waiting for deployment kube-system/csi-azuredisk-controller to be available - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:88 @ 01/16/23 17:12:09.115
Jan 16 17:12:09.115: INFO: starting to wait for deployment to become available
Jan 16 17:12:49.621: INFO: Deployment kube-system/csi-azuredisk-controller is now available, took 40.506288837s
STEP: Waiting for Running azure-disk-csi node pods - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cloud-provider-azure.go:86 @ 01/16/23 17:12:49.621
STEP: waiting for daemonset kube-system/csi-azuredisk-node to be complete - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:88 @ 01/16/23 17:12:49.763
Jan 16 17:12:49.763: INFO: waiting for daemonset kube-system/csi-azuredisk-node to be complete
Jan 16 17:12:49.790: INFO: 1 daemonset kube-system/csi-azuredisk-node pods are running, took 27.632665ms
STEP: waiting for daemonset kube-system/csi-azuredisk-node-win to be complete - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:88 @ 01/16/23 17:12:49.926
Jan 16 17:12:49.926: INFO: waiting for daemonset kube-system/csi-azuredisk-node-win to be complete
Jan 16 17:12:49.953: INFO: 0 daemonset kube-system/csi-azuredisk-node-win pods are running, took 27.251376ms
INFO: Waiting for control plane to be ready
INFO: Waiting for control plane capz-conf-vmxw18/capz-conf-vmxw18-control-plane to be ready (implies underlying nodes to be ready as well)
STEP: Waiting for the control plane to be ready - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/controlplane_helpers.go:165 @ 01/16/23 17:12:49.973
STEP: Checking all the control plane machines are in the expected failure domains - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/controlplane_helpers.go:196 @ 01/16/23 17:12:49.983
INFO: Waiting for the machine deployments to be provisioned
STEP: Waiting for the workload nodes to exist - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/machinedeployment_helpers.go:102 @ 01/16/23 17:12:50.012
STEP: Checking all the machines controlled by capz-conf-vmxw18-md-0 are in the "<None>" failure domain - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/ginkgoextensions/output.go:35 @ 01/16/23 17:13:20.074
STEP: Waiting for the workload nodes to exist - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/machinedeployment_helpers.go:102 @ 01/16/23 17:13:20.089
STEP: Checking all the machines controlled by capz-conf-vmxw18-md-win are in the "<None>" failure domain - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/ginkgoextensions/output.go:35 @ 01/16/23 17:13:20.105
INFO: Waiting for the machine pools to be provisioned
STEP: Running e2e test: dir=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e, command=["-nodes=25" "-slowSpecThreshold=120" "/usr/local/bin/e2e.test" "--" "--report-dir=/output" "--e2e-output-dir=/output/e2e-output" "--dump-logs-on-failure=false" "--report-prefix=kubetest." "--num-nodes=2" "--kubeconfig=/tmp/kubeconfig" "--provider=skeleton" "-ginkgo.slow-spec-threshold=120s" "-ginkgo.timeout=3h" "-ginkgo.trace=true" "-ginkgo.v=true" "-disable-log-dump=true" "-ginkgo.focus=\\[Conformance\\]" "-ginkgo.progress=true" "-ginkgo.skip=\\[Serial\\]"] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/ginkgoextensions/output.go:35 @ 01/16/23 17:13:20.177
Running Suite: Kubernetes e2e suite - /usr/local/bin
====================================================
Random Seed: �[1m1673889200�[0m - will randomize all specs

Will run �[1m344�[0m of �[1m7072�[0m specs
Running in parallel across �[1m25�[0m processes
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [636.833 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.58�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [637.040 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.581�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [637.693 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;243mTimeline >>�[0m
  Jan 16 17:13:22.880: INFO: >>> kubeConfig: /tmp/kubeconfig
  Jan 16 17:13:22.883: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
  Jan 16 17:13:23.103: INFO: Condition Ready of node capz-conf-vmxw18-md-0-2zlxc is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready  NoSchedule <nil>} {node.kubernetes.io/not-ready  NoExecute 2023-01-16 17:13:04 +0000 UTC}]. Failure
  Jan 16 17:13:23.103: INFO: Condition Ready of node capz-conf-vmxw18-md-0-chndb is true, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready  NoExecute 2023-01-16 17:12:54 +0000 UTC}]. Failure
  Jan 16 17:13:23.103: INFO: Unschedulable nodes= 2, maximum value for starting tests= 0
  Jan 16 17:13:23.103: INFO: 	-> Node capz-conf-vmxw18-md-0-2zlxc [[[ Ready=false, Network(available)=false, Taints=[{node.kubernetes.io/not-ready  NoSchedule <nil>} {node.kubernetes.io/not-ready  NoExecute 2023-01-16 17:13:04 +0000 UTC}], NonblockingTaints=node-role.kubernetes.io/control-plane,node-role.kubernetes.io/master ]]]
  Jan 16 17:13:23.103: INFO: 	-> Node capz-conf-vmxw18-md-0-chndb [[[ Ready=false, Network(available)=false, Taints=[{node.kubernetes.io/not-ready  NoExecute 2023-01-16 17:12:54 +0000 UTC}], NonblockingTaints=node-role.kubernetes.io/control-plane,node-role.kubernetes.io/master ]]]
  Jan 16 17:13:23.103: INFO: ==== node wait: 1 out of 3 nodes are ready, max notReady allowed 0.  Need 2 more before starting.
  Jan 16 17:13:53.150: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
  Jan 16 17:13:53.336: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:13:53.336: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:13:53.336: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:13:53.336: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
  Jan 16 17:13:53.336: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:13:53.336: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:13:53.336: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:13:53.336: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:13:53.336: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:13:53.336: INFO: 
  Jan 16 17:13:55.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:13:55.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:13:55.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:13:55.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
  Jan 16 17:13:55.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:13:55.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:13:55.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:13:55.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:13:55.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:13:55.459: INFO: 
  Jan 16 17:13:57.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:13:57.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:13:57.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:13:57.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
  Jan 16 17:13:57.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:13:57.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:13:57.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:13:57.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:13:57.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:13:57.455: INFO: 
  Jan 16 17:13:59.468: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:13:59.468: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:13:59.468: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:13:59.468: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
  Jan 16 17:13:59.468: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:13:59.468: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:13:59.468: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:13:59.468: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:13:59.468: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:13:59.468: INFO: 
  Jan 16 17:14:01.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:01.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:01.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:01.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
  Jan 16 17:14:01.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:01.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:01.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:01.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:01.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:01.459: INFO: 
  Jan 16 17:14:03.461: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:03.461: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:03.461: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:03.461: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
  Jan 16 17:14:03.461: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:03.461: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:03.461: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:03.461: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:03.461: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:03.461: INFO: 
  Jan 16 17:14:05.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:05.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:05.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:05.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
  Jan 16 17:14:05.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:05.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:05.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:05.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:05.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:05.454: INFO: 
  Jan 16 17:14:07.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:07.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:07.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:07.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
  Jan 16 17:14:07.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:07.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:07.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:07.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:07.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:07.457: INFO: 
  Jan 16 17:14:09.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:09.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:09.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:09.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
  Jan 16 17:14:09.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:09.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:09.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:09.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:09.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:09.454: INFO: 
  Jan 16 17:14:11.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:11.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:11.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:11.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
  Jan 16 17:14:11.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:11.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:11.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:11.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:11.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:11.454: INFO: 
  Jan 16 17:14:13.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:13.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:13.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:13.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
  Jan 16 17:14:13.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:13.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:13.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:13.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:13.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:13.454: INFO: 
  Jan 16 17:14:15.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:15.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:15.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:15.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
  Jan 16 17:14:15.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:15.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:15.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:15.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:15.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:15.452: INFO: 
  Jan 16 17:14:17.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:17.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:17.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:17.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
  Jan 16 17:14:17.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:17.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:17.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:17.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:17.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:17.453: INFO: 
  Jan 16 17:14:19.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:19.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:19.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:19.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
  Jan 16 17:14:19.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:19.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:19.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:19.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:19.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:19.454: INFO: 
  Jan 16 17:14:21.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:21.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:21.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:21.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
  Jan 16 17:14:21.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:21.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:21.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:21.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:21.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:21.457: INFO: 
  Jan 16 17:14:23.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:23.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:23.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:23.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
  Jan 16 17:14:23.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:23.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:23.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:23.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:23.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:23.459: INFO: 
  Jan 16 17:14:25.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:25.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:25.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:25.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
  Jan 16 17:14:25.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:25.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:25.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:25.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:25.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:25.454: INFO: 
  Jan 16 17:14:27.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:27.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:27.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:27.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
  Jan 16 17:14:27.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:27.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:27.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:27.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:27.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:27.455: INFO: 
  Jan 16 17:14:29.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:29.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:29.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:29.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
  Jan 16 17:14:29.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:29.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:29.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:29.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:29.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:29.453: INFO: 
  Jan 16 17:14:31.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:31.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:31.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:31.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
  Jan 16 17:14:31.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:31.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:31.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:31.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:31.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:31.454: INFO: 
  Jan 16 17:14:33.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:33.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:33.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:33.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
  Jan 16 17:14:33.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:33.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:33.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:33.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:33.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:33.454: INFO: 
  Jan 16 17:14:35.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:35.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:35.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:35.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
  Jan 16 17:14:35.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:35.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:35.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:35.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:35.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:35.452: INFO: 
  Jan 16 17:14:37.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:37.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:37.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:37.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
  Jan 16 17:14:37.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:37.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:37.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:37.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:37.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:37.453: INFO: 
  Jan 16 17:14:39.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:39.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:39.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:39.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
  Jan 16 17:14:39.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:39.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:39.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:39.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:39.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:39.454: INFO: 
  Jan 16 17:14:41.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:41.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:41.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:41.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
  Jan 16 17:14:41.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:41.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:41.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:41.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:41.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:41.455: INFO: 
  Jan 16 17:14:43.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:43.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:43.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:43.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
  Jan 16 17:14:43.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:43.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:43.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:43.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:43.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:43.456: INFO: 
  Jan 16 17:14:45.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:45.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:45.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:45.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
  Jan 16 17:14:45.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:45.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:45.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:45.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:45.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:45.458: INFO: 
  Jan 16 17:14:47.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:47.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:47.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:47.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
  Jan 16 17:14:47.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:47.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:47.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:47.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:47.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:47.454: INFO: 
  Jan 16 17:14:49.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:49.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:49.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:49.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
  Jan 16 17:14:49.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:49.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:49.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:49.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:49.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:49.454: INFO: 
  Jan 16 17:14:51.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:51.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:51.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:51.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
  Jan 16 17:14:51.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:51.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:51.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:51.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:51.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:51.456: INFO: 
  Jan 16 17:14:53.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:53.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:53.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:53.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
  Jan 16 17:14:53.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:53.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:53.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:53.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:53.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:53.454: INFO: 
  Jan 16 17:14:55.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:55.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:55.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:55.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
  Jan 16 17:14:55.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:55.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:55.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:55.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:55.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:55.456: INFO: 
  Jan 16 17:14:57.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:57.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:57.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:57.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
  Jan 16 17:14:57.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:57.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:57.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:57.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:57.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:57.453: INFO: 
  Jan 16 17:14:59.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:59.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:59.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:14:59.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
  Jan 16 17:14:59.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:14:59.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:14:59.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:59.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:14:59.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:14:59.455: INFO: 
  Jan 16 17:15:01.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:01.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:01.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:01.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
  Jan 16 17:15:01.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:01.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:01.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:01.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:01.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:01.456: INFO: 
  Jan 16 17:15:03.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:03.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:03.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:03.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
  Jan 16 17:15:03.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:03.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:03.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:03.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:03.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:03.454: INFO: 
  Jan 16 17:15:05.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:05.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:05.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:05.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
  Jan 16 17:15:05.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:05.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:05.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:05.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:05.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:05.456: INFO: 
  Jan 16 17:15:07.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:07.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:07.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:07.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
  Jan 16 17:15:07.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:07.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:07.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:07.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:07.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:07.455: INFO: 
  Jan 16 17:15:09.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:09.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:09.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:09.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
  Jan 16 17:15:09.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:09.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:09.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:09.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:09.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:09.454: INFO: 
  Jan 16 17:15:11.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:11.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:11.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:11.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
  Jan 16 17:15:11.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:11.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:11.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:11.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:11.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:11.452: INFO: 
  Jan 16 17:15:13.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:13.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:13.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:13.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
  Jan 16 17:15:13.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:13.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:13.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:13.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:13.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:13.455: INFO: 
  Jan 16 17:15:15.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:15.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:15.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:15.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
  Jan 16 17:15:15.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:15.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:15.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:15.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:15.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:15.453: INFO: 
  Jan 16 17:15:17.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:17.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:17.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:17.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
  Jan 16 17:15:17.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:17.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:17.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:17.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:17.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:17.455: INFO: 
  Jan 16 17:15:19.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:19.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:19.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:19.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
  Jan 16 17:15:19.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:19.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:19.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:19.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:19.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:19.454: INFO: 
  Jan 16 17:15:21.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:21.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:21.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:21.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
  Jan 16 17:15:21.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:21.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:21.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:21.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:21.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:21.454: INFO: 
  Jan 16 17:15:23.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:23.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:23.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:23.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
  Jan 16 17:15:23.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:23.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:23.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:23.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:23.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:23.453: INFO: 
  Jan 16 17:15:25.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:25.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:25.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:25.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
  Jan 16 17:15:25.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:25.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:25.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:25.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:25.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:25.453: INFO: 
  Jan 16 17:15:27.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:27.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:27.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:27.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
  Jan 16 17:15:27.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:27.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:27.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:27.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:27.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:27.454: INFO: 
  Jan 16 17:15:29.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:29.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:29.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:29.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
  Jan 16 17:15:29.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:29.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:29.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:29.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:29.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:29.455: INFO: 
  Jan 16 17:15:31.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:31.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:31.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:31.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
  Jan 16 17:15:31.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:31.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:31.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:31.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:31.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:31.454: INFO: 
  Jan 16 17:15:33.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:33.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:33.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:33.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
  Jan 16 17:15:33.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:33.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:33.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:33.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:33.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:33.455: INFO: 
  Jan 16 17:15:35.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:35.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:35.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:35.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
  Jan 16 17:15:35.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:35.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:35.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:35.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:35.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:35.452: INFO: 
  Jan 16 17:15:37.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:37.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:37.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:37.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
  Jan 16 17:15:37.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:37.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:37.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:37.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:37.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:37.453: INFO: 
  Jan 16 17:15:39.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:39.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:39.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:39.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
  Jan 16 17:15:39.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:39.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:39.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:39.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:39.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:39.456: INFO: 
  Jan 16 17:15:41.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:41.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:41.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:41.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
  Jan 16 17:15:41.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:41.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:41.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:41.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:41.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:41.453: INFO: 
  Jan 16 17:15:43.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:43.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:43.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:43.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
  Jan 16 17:15:43.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:43.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:43.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:43.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:43.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:43.452: INFO: 
  Jan 16 17:15:45.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:45.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:45.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:45.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
  Jan 16 17:15:45.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:45.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:45.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:45.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:45.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:45.453: INFO: 
  Jan 16 17:15:47.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:47.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:47.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:47.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
  Jan 16 17:15:47.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:47.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:47.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:47.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:47.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:47.456: INFO: 
  Jan 16 17:15:49.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:49.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:49.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:49.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
  Jan 16 17:15:49.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:49.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:49.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:49.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:49.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:49.457: INFO: 
  Jan 16 17:15:51.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:51.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:51.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:51.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
  Jan 16 17:15:51.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:51.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:51.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:51.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:51.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:51.453: INFO: 
  Jan 16 17:15:53.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:53.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:53.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:53.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
  Jan 16 17:15:53.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:53.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:53.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:53.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:53.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:53.457: INFO: 
  Jan 16 17:15:55.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:55.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:55.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:55.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
  Jan 16 17:15:55.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:55.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:55.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:55.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:55.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:55.454: INFO: 
  Jan 16 17:15:57.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:57.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:57.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:57.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
  Jan 16 17:15:57.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:57.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:57.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:57.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:57.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:57.458: INFO: 
  Jan 16 17:15:59.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:59.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:59.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:15:59.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
  Jan 16 17:15:59.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:15:59.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:15:59.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:59.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:15:59.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:15:59.457: INFO: 
  Jan 16 17:16:01.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:01.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:01.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:01.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
  Jan 16 17:16:01.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:01.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:01.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:01.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:01.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:01.455: INFO: 
  Jan 16 17:16:03.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:03.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:03.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:03.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
  Jan 16 17:16:03.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:03.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:03.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:03.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:03.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:03.454: INFO: 
  Jan 16 17:16:05.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:05.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:05.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:05.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
  Jan 16 17:16:05.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:05.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:05.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:05.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:05.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:05.453: INFO: 
  Jan 16 17:16:07.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:07.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:07.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:07.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
  Jan 16 17:16:07.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:07.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:07.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:07.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:07.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:07.454: INFO: 
  Jan 16 17:16:09.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:09.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:09.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:09.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
  Jan 16 17:16:09.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:09.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:09.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:09.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:09.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:09.453: INFO: 
  Jan 16 17:16:11.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:11.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:11.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:11.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
  Jan 16 17:16:11.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:11.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:11.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:11.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:11.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:11.453: INFO: 
  Jan 16 17:16:13.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:13.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:13.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:13.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
  Jan 16 17:16:13.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:13.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:13.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:13.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:13.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:13.454: INFO: 
  Jan 16 17:16:15.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:15.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:15.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:15.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
  Jan 16 17:16:15.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:15.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:15.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:15.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:15.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:15.453: INFO: 
  Jan 16 17:16:17.464: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:17.464: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:17.464: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:17.464: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
  Jan 16 17:16:17.464: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:17.464: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:17.464: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:17.464: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:17.464: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:17.464: INFO: 
  Jan 16 17:16:19.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:19.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:19.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:19.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
  Jan 16 17:16:19.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:19.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:19.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:19.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:19.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:19.453: INFO: 
  Jan 16 17:16:21.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:21.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:21.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:21.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
  Jan 16 17:16:21.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:21.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:21.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:21.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:21.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:21.452: INFO: 
  Jan 16 17:16:23.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:23.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:23.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:23.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
  Jan 16 17:16:23.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:23.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:23.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:23.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:23.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:23.452: INFO: 
  Jan 16 17:16:25.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:25.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:25.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:25.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
  Jan 16 17:16:25.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:25.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:25.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:25.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:25.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:25.455: INFO: 
  Jan 16 17:16:27.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:27.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:27.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:27.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
  Jan 16 17:16:27.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:27.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:27.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:27.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:27.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:27.453: INFO: 
  Jan 16 17:16:29.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:29.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:29.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:29.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
  Jan 16 17:16:29.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:29.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:29.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:29.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:29.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:29.455: INFO: 
  Jan 16 17:16:31.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:31.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:31.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:31.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
  Jan 16 17:16:31.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:31.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:31.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:31.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:31.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:31.454: INFO: 
  Jan 16 17:16:33.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:33.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:33.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:33.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
  Jan 16 17:16:33.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:33.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:33.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:33.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:33.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:33.455: INFO: 
  Jan 16 17:16:35.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:35.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:35.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:35.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
  Jan 16 17:16:35.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:35.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:35.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:35.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:35.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:35.455: INFO: 
  Jan 16 17:16:37.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:37.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:37.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:37.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
  Jan 16 17:16:37.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:37.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:37.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:37.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:37.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:37.455: INFO: 
  Jan 16 17:16:39.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:39.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:39.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:39.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
  Jan 16 17:16:39.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:39.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:39.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:39.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:39.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:39.454: INFO: 
  Jan 16 17:16:41.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:41.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:41.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:41.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
  Jan 16 17:16:41.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:41.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:41.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:41.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:41.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:41.455: INFO: 
  Jan 16 17:16:43.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:43.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:43.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:43.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
  Jan 16 17:16:43.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:43.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:43.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:43.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:43.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:43.453: INFO: 
  Jan 16 17:16:45.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:45.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:45.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:45.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
  Jan 16 17:16:45.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:45.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:45.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:45.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:45.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:45.453: INFO: 
  Jan 16 17:16:47.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:47.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:47.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:47.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
  Jan 16 17:16:47.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:47.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:47.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:47.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:47.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:47.454: INFO: 
  Jan 16 17:16:49.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:49.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:49.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:49.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
  Jan 16 17:16:49.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:49.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:49.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:49.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:49.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:49.456: INFO: 
  Jan 16 17:16:51.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:51.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:51.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:51.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
  Jan 16 17:16:51.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:51.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:51.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:51.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:51.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:51.452: INFO: 
  Jan 16 17:16:53.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:53.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:53.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:53.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
  Jan 16 17:16:53.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:53.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:53.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:53.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:53.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:53.455: INFO: 
  Jan 16 17:16:55.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:55.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:55.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:55.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
  Jan 16 17:16:55.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:55.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:55.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:55.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:55.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:55.454: INFO: 
  Jan 16 17:16:57.474: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:57.474: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:57.474: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:57.474: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
  Jan 16 17:16:57.474: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:57.474: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:57.474: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:57.474: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:57.474: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:57.474: INFO: 
  Jan 16 17:16:59.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:59.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:59.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:16:59.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
  Jan 16 17:16:59.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:16:59.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:16:59.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:59.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:16:59.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:16:59.455: INFO: 
  Jan 16 17:17:01.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:01.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:01.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:01.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
  Jan 16 17:17:01.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:01.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:01.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:01.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:01.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:01.457: INFO: 
  Jan 16 17:17:03.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:03.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:03.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:03.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
  Jan 16 17:17:03.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:03.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:03.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:03.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:03.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:03.454: INFO: 
  Jan 16 17:17:05.462: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:05.462: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:05.462: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:05.462: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
  Jan 16 17:17:05.462: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:05.462: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:05.462: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:05.462: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:05.462: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:05.462: INFO: 
  Jan 16 17:17:07.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:07.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:07.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:07.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
  Jan 16 17:17:07.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:07.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:07.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:07.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:07.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:07.457: INFO: 
  Jan 16 17:17:09.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:09.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:09.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:09.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
  Jan 16 17:17:09.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:09.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:09.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:09.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:09.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:09.454: INFO: 
  Jan 16 17:17:11.460: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:11.460: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:11.460: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:11.460: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
  Jan 16 17:17:11.460: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:11.460: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:11.460: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:11.460: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:11.460: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:11.460: INFO: 
  Jan 16 17:17:13.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:13.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:13.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:13.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
  Jan 16 17:17:13.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:13.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:13.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:13.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:13.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:13.453: INFO: 
  Jan 16 17:17:15.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:15.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:15.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:15.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
  Jan 16 17:17:15.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:15.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:15.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:15.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:15.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:15.455: INFO: 
  Jan 16 17:17:17.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:17.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:17.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:17.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
  Jan 16 17:17:17.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:17.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:17.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:17.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:17.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:17.458: INFO: 
  Jan 16 17:17:19.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:19.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:19.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:19.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
  Jan 16 17:17:19.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:19.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:19.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:19.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:19.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:19.454: INFO: 
  Jan 16 17:17:21.451: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:21.451: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:21.451: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:21.451: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
  Jan 16 17:17:21.451: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:21.451: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:21.451: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:21.451: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:21.451: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:21.451: INFO: 
  Jan 16 17:17:23.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:23.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:23.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:23.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
  Jan 16 17:17:23.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:23.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:23.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:23.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:23.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:23.453: INFO: 
  Jan 16 17:17:25.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:25.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:25.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:25.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
  Jan 16 17:17:25.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:25.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:25.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:25.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:25.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:25.454: INFO: 
  Jan 16 17:17:27.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:27.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:27.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:27.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
  Jan 16 17:17:27.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:27.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:27.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:27.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:27.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:27.456: INFO: 
  Jan 16 17:17:29.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:29.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:29.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:29.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
  Jan 16 17:17:29.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:29.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:29.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:29.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:29.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:29.454: INFO: 
  Jan 16 17:17:31.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:31.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:31.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:31.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
  Jan 16 17:17:31.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:31.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:31.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:31.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:31.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:31.455: INFO: 
  Jan 16 17:17:33.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:33.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:33.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:33.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
  Jan 16 17:17:33.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:33.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:33.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:33.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:33.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:33.453: INFO: 
  Jan 16 17:17:35.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:35.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:35.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:35.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
  Jan 16 17:17:35.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:35.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:35.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:35.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:35.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:35.456: INFO: 
  Jan 16 17:17:37.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:37.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:37.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:37.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
  Jan 16 17:17:37.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:37.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:37.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:37.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:37.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:37.453: INFO: 
  Jan 16 17:17:39.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:39.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:39.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:39.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
  Jan 16 17:17:39.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:39.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:39.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:39.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:39.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:39.455: INFO: 
  Jan 16 17:17:41.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:41.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:41.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:41.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
  Jan 16 17:17:41.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:41.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:41.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:41.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:41.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:41.455: INFO: 
  Jan 16 17:17:43.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:43.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:43.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:43.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
  Jan 16 17:17:43.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:43.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:43.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:43.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:43.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:43.453: INFO: 
  Jan 16 17:17:45.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:45.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:45.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:45.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
  Jan 16 17:17:45.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:45.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:45.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:45.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:45.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:45.453: INFO: 
  Jan 16 17:17:47.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:47.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:47.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:47.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
  Jan 16 17:17:47.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:47.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:47.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:47.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:47.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:47.453: INFO: 
  Jan 16 17:17:49.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:49.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:49.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:49.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
  Jan 16 17:17:49.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:49.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:49.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:49.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:49.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:49.455: INFO: 
  Jan 16 17:17:51.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:51.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:51.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:51.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
  Jan 16 17:17:51.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:51.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:51.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:51.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:51.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:51.454: INFO: 
  Jan 16 17:17:53.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:53.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:53.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:53.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
  Jan 16 17:17:53.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:53.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:53.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:53.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:53.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:53.454: INFO: 
  Jan 16 17:17:55.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:55.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:55.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:55.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
  Jan 16 17:17:55.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:55.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:55.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:55.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:55.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:55.455: INFO: 
  Jan 16 17:17:57.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:57.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:57.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:57.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
  Jan 16 17:17:57.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:57.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:57.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:57.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:57.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:57.459: INFO: 
  Jan 16 17:17:59.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:59.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:59.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:17:59.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
  Jan 16 17:17:59.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:17:59.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:17:59.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:59.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:17:59.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:17:59.453: INFO: 
  Jan 16 17:18:01.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:01.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:01.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:01.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
  Jan 16 17:18:01.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:01.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:01.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:01.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:01.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:01.455: INFO: 
  Jan 16 17:18:03.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:03.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:03.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:03.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
  Jan 16 17:18:03.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:03.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:03.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:03.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:03.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:03.453: INFO: 
  Jan 16 17:18:05.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:05.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:05.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:05.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
  Jan 16 17:18:05.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:05.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:05.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:05.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:05.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:05.453: INFO: 
  Jan 16 17:18:07.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:07.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:07.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:07.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
  Jan 16 17:18:07.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:07.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:07.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:07.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:07.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:07.455: INFO: 
  Jan 16 17:18:09.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:09.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:09.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:09.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
  Jan 16 17:18:09.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:09.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:09.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:09.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:09.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:09.457: INFO: 
  Jan 16 17:18:11.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:11.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:11.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:11.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
  Jan 16 17:18:11.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:11.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:11.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:11.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:11.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:11.456: INFO: 
  Jan 16 17:18:13.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:13.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:13.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:13.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
  Jan 16 17:18:13.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:13.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:13.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:13.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:13.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:13.453: INFO: 
  Jan 16 17:18:15.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:15.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:15.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:15.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
  Jan 16 17:18:15.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:15.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:15.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:15.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:15.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:15.453: INFO: 
  Jan 16 17:18:17.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:17.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:17.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:17.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
  Jan 16 17:18:17.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:17.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:17.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:17.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:17.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:17.453: INFO: 
  Jan 16 17:18:19.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:19.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:19.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:19.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
  Jan 16 17:18:19.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:19.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:19.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:19.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:19.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:19.454: INFO: 
  Jan 16 17:18:21.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:21.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:21.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:21.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
  Jan 16 17:18:21.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:21.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:21.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:21.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:21.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:21.452: INFO: 
  Jan 16 17:18:23.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:23.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:23.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:23.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
  Jan 16 17:18:23.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:23.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:23.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:23.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:23.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:23.455: INFO: 
  Jan 16 17:18:25.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:25.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:25.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:25.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
  Jan 16 17:18:25.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:25.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:25.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:25.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:25.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:25.453: INFO: 
  Jan 16 17:18:27.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:27.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:27.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:27.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
  Jan 16 17:18:27.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:27.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:27.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:27.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:27.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:27.455: INFO: 
  Jan 16 17:18:29.464: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:29.464: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:29.464: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:29.464: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
  Jan 16 17:18:29.464: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:29.464: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:29.464: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:29.464: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:29.464: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:29.464: INFO: 
  Jan 16 17:18:31.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:31.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:31.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:31.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
  Jan 16 17:18:31.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:31.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:31.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:31.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:31.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:31.453: INFO: 
  Jan 16 17:18:33.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:33.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:33.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:33.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
  Jan 16 17:18:33.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:33.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:33.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:33.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:33.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:33.453: INFO: 
  Jan 16 17:18:35.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:35.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:35.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:35.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
  Jan 16 17:18:35.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:35.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:35.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:35.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:35.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:35.454: INFO: 
  Jan 16 17:18:37.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:37.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:37.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:37.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
  Jan 16 17:18:37.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:37.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:37.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:37.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:37.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:37.456: INFO: 
  Jan 16 17:18:39.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:39.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:39.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:39.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
  Jan 16 17:18:39.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:39.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:39.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:39.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:39.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:39.459: INFO: 
  Jan 16 17:18:41.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:41.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:41.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:41.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
  Jan 16 17:18:41.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:41.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:41.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:41.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:41.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:41.453: INFO: 
  Jan 16 17:18:43.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:43.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:43.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:43.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
  Jan 16 17:18:43.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:43.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:43.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:43.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:43.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:43.454: INFO: 
  Jan 16 17:18:45.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:45.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:45.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:45.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
  Jan 16 17:18:45.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:45.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:45.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:45.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:45.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:45.452: INFO: 
  Jan 16 17:18:47.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:47.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:47.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:47.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
  Jan 16 17:18:47.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:47.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:47.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:47.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:47.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:47.455: INFO: 
  Jan 16 17:18:49.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:49.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:49.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:49.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
  Jan 16 17:18:49.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:49.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:49.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:49.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:49.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:49.452: INFO: 
  Jan 16 17:18:51.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:51.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:51.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:51.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
  Jan 16 17:18:51.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:51.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:51.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:51.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:51.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:51.456: INFO: 
  Jan 16 17:18:53.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:53.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:53.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:53.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
  Jan 16 17:18:53.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:53.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:53.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:53.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:53.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:53.453: INFO: 
  Jan 16 17:18:55.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:55.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:55.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:55.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
  Jan 16 17:18:55.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:55.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:55.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:55.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:55.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:55.453: INFO: 
  Jan 16 17:18:57.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:57.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:57.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:57.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
  Jan 16 17:18:57.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:57.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:57.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:57.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:57.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:57.454: INFO: 
  Jan 16 17:18:59.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:59.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:59.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:18:59.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
  Jan 16 17:18:59.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:18:59.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:18:59.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:59.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:18:59.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:18:59.454: INFO: 
  Jan 16 17:19:01.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:01.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:01.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:01.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
  Jan 16 17:19:01.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:01.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:01.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:01.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:01.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:01.452: INFO: 
  Jan 16 17:19:03.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:03.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:03.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:03.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
  Jan 16 17:19:03.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:03.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:03.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:03.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:03.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:03.452: INFO: 
  Jan 16 17:19:05.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:05.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:05.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:05.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
  Jan 16 17:19:05.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:05.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:05.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:05.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:05.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:05.452: INFO: 
  Jan 16 17:19:07.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:07.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:07.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:07.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
  Jan 16 17:19:07.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:07.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:07.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:07.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:07.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:07.454: INFO: 
  Jan 16 17:19:09.464: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:09.464: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:09.464: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:09.464: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
  Jan 16 17:19:09.464: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:09.464: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:09.464: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:09.464: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:09.464: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:09.464: INFO: 
  Jan 16 17:19:11.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:11.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:11.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:11.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
  Jan 16 17:19:11.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:11.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:11.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:11.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:11.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:11.457: INFO: 
  Jan 16 17:19:13.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:13.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:13.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:13.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
  Jan 16 17:19:13.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:13.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:13.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:13.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:13.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:13.457: INFO: 
  Jan 16 17:19:15.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:15.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:15.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:15.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
  Jan 16 17:19:15.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:15.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:15.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:15.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:15.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:15.458: INFO: 
  Jan 16 17:19:17.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:17.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:17.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:17.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
  Jan 16 17:19:17.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:17.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:17.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:17.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:17.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:17.458: INFO: 
  Jan 16 17:19:19.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:19.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:19.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:19.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
  Jan 16 17:19:19.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:19.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:19.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:19.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:19.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:19.456: INFO: 
  Jan 16 17:19:21.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:21.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:21.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:21.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
  Jan 16 17:19:21.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:21.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:21.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:21.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:21.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:21.458: INFO: 
  Jan 16 17:19:23.468: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:23.468: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:23.468: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:23.468: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
  Jan 16 17:19:23.468: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:23.468: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:23.468: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:23.468: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:23.468: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:23.469: INFO: 
  Jan 16 17:19:25.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:25.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:25.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:25.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
  Jan 16 17:19:25.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:25.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:25.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:25.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:25.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:25.456: INFO: 
  Jan 16 17:19:27.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:27.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:27.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:27.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
  Jan 16 17:19:27.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:27.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:27.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:27.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:27.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:27.457: INFO: 
  Jan 16 17:19:29.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:29.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:29.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:29.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
  Jan 16 17:19:29.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:29.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:29.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:29.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:29.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:29.459: INFO: 
  Jan 16 17:19:31.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:31.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:31.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:31.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
  Jan 16 17:19:31.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:31.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:31.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:31.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:31.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:31.458: INFO: 
  Jan 16 17:19:33.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:33.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:33.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:33.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
  Jan 16 17:19:33.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:33.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:33.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:33.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:33.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:33.458: INFO: 
  Jan 16 17:19:35.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:35.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:35.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:35.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
  Jan 16 17:19:35.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:35.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:35.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:35.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:35.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:35.456: INFO: 
  Jan 16 17:19:37.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:37.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:37.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:37.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
  Jan 16 17:19:37.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:37.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:37.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:37.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:37.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:37.458: INFO: 
  Jan 16 17:19:39.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:39.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:39.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:39.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
  Jan 16 17:19:39.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:39.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:39.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:39.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:39.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:39.458: INFO: 
  Jan 16 17:19:41.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:41.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:41.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:41.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
  Jan 16 17:19:41.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:41.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:41.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:41.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:41.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:41.458: INFO: 
  Jan 16 17:19:43.463: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:43.463: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:43.463: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:43.463: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
  Jan 16 17:19:43.463: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:43.463: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:43.463: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:43.463: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:43.463: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:43.463: INFO: 
  Jan 16 17:19:45.467: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:45.467: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:45.467: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:45.467: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
  Jan 16 17:19:45.467: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:45.467: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:45.467: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:45.467: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:45.467: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:45.467: INFO: 
  Jan 16 17:19:47.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:47.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:47.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:47.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
  Jan 16 17:19:47.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:47.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:47.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:47.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:47.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:47.454: INFO: 
  Jan 16 17:19:49.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:49.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:49.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:49.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
  Jan 16 17:19:49.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:49.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:49.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:49.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:49.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:49.459: INFO: 
  Jan 16 17:19:51.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:51.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:51.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:51.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
  Jan 16 17:19:51.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:51.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:51.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:51.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:51.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:51.459: INFO: 
  Jan 16 17:19:53.461: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:53.461: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:53.461: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:53.461: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
  Jan 16 17:19:53.461: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:53.461: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:53.461: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:53.461: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:53.461: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:53.461: INFO: 
  Jan 16 17:19:55.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:55.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:55.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:55.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
  Jan 16 17:19:55.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:55.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:55.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:55.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:55.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:55.456: INFO: 
  Jan 16 17:19:57.475: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:57.475: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:57.475: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:57.475: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
  Jan 16 17:19:57.475: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:57.475: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:57.475: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:57.475: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:57.475: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:57.475: INFO: 
  Jan 16 17:19:59.465: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:59.465: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:59.465: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:19:59.465: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
  Jan 16 17:19:59.465: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:19:59.465: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:19:59.465: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:59.465: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:19:59.465: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:19:59.465: INFO: 
  Jan 16 17:20:01.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:01.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:01.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:01.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
  Jan 16 17:20:01.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:01.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:01.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:01.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:01.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:01.458: INFO: 
  Jan 16 17:20:03.460: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:03.460: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:03.460: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:03.460: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
  Jan 16 17:20:03.460: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:03.460: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:03.460: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:03.460: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:03.460: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:03.460: INFO: 
  Jan 16 17:20:05.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:05.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:05.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:05.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
  Jan 16 17:20:05.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:05.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:05.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:05.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:05.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:05.459: INFO: 
  Jan 16 17:20:07.462: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:07.462: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:07.462: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:07.463: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
  Jan 16 17:20:07.463: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:07.463: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:07.463: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:07.463: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:07.463: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:07.463: INFO: 
  Jan 16 17:20:09.462: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:09.463: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:09.463: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:09.463: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
  Jan 16 17:20:09.463: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:09.463: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:09.463: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:09.463: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:09.463: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:09.463: INFO: 
  Jan 16 17:20:11.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:11.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:11.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:11.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
  Jan 16 17:20:11.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:11.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:11.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:11.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:11.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:11.460: INFO: 
  Jan 16 17:20:13.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:13.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:13.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:13.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
  Jan 16 17:20:13.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:13.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:13.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:13.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:13.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:13.456: INFO: 
  Jan 16 17:20:15.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:15.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:15.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:15.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
  Jan 16 17:20:15.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:15.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:15.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:15.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:15.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:15.452: INFO: 
  Jan 16 17:20:17.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:17.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:17.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:17.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
  Jan 16 17:20:17.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:17.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:17.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:17.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:17.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:17.457: INFO: 
  Jan 16 17:20:19.462: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:19.462: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:19.462: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:19.462: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
  Jan 16 17:20:19.462: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:19.462: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:19.462: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:19.462: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:19.462: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:19.462: INFO: 
  Jan 16 17:20:21.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:21.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:21.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:21.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
  Jan 16 17:20:21.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:21.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:21.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:21.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:21.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:21.459: INFO: 
  Jan 16 17:20:23.462: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:23.462: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:23.462: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:23.462: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
  Jan 16 17:20:23.462: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:23.462: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:23.462: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:23.462: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:23.462: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:23.462: INFO: 
  Jan 16 17:20:25.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:25.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:25.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:25.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
  Jan 16 17:20:25.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:25.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:25.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:25.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:25.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:25.458: INFO: 
  Jan 16 17:20:27.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:27.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:27.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:27.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
  Jan 16 17:20:27.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:27.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:27.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:27.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:27.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:27.459: INFO: 
  Jan 16 17:20:29.462: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:29.462: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:29.462: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:29.462: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
  Jan 16 17:20:29.462: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:29.462: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:29.462: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:29.462: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:29.462: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:29.462: INFO: 
  Jan 16 17:20:31.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:31.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:31.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:31.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
  Jan 16 17:20:31.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:31.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:31.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:31.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:31.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:31.459: INFO: 
  Jan 16 17:20:33.460: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:33.460: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:33.460: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:33.460: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
  Jan 16 17:20:33.460: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:33.460: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:33.460: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:33.460: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:33.460: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:33.460: INFO: 
  Jan 16 17:20:35.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:35.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:35.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:35.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
  Jan 16 17:20:35.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:35.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:35.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:35.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:35.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:35.456: INFO: 
  Jan 16 17:20:37.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:37.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:37.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:37.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
  Jan 16 17:20:37.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:37.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:37.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:37.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:37.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:37.458: INFO: 
  Jan 16 17:20:39.463: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:39.463: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:39.463: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:39.463: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
  Jan 16 17:20:39.463: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:39.463: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:39.463: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:39.463: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:39.463: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:39.463: INFO: 
  Jan 16 17:20:41.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:41.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:41.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:41.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
  Jan 16 17:20:41.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:41.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:41.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:41.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:41.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:41.458: INFO: 
  Jan 16 17:20:43.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:43.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:43.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:43.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
  Jan 16 17:20:43.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:43.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:43.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:43.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:43.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:43.457: INFO: 
  Jan 16 17:20:45.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:45.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:45.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:45.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
  Jan 16 17:20:45.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:45.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:45.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:45.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:45.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:45.459: INFO: 
  Jan 16 17:20:47.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:47.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:47.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:47.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
  Jan 16 17:20:47.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:47.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:47.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:47.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:47.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:47.457: INFO: 
  Jan 16 17:20:49.460: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:49.460: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:49.460: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:49.460: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
  Jan 16 17:20:49.460: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:49.460: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:49.460: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:49.460: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:49.460: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:49.460: INFO: 
  Jan 16 17:20:51.461: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:51.461: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:51.461: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:51.461: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
  Jan 16 17:20:51.461: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:51.461: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:51.461: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:51.461: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:51.461: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:51.462: INFO: 
  Jan 16 17:20:53.461: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:53.461: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:53.461: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:53.461: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
  Jan 16 17:20:53.461: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:53.461: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:53.461: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:53.461: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:53.461: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:53.461: INFO: 
  Jan 16 17:20:55.463: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:55.463: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:55.463: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:55.463: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
  Jan 16 17:20:55.463: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:55.463: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:55.463: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:55.463: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:55.463: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:55.463: INFO: 
  Jan 16 17:20:57.463: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:57.463: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:57.463: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:57.463: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
  Jan 16 17:20:57.463: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:57.463: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:57.463: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:57.463: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:57.463: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:57.463: INFO: 
  Jan 16 17:20:59.460: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:59.460: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:59.460: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:20:59.460: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
  Jan 16 17:20:59.460: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:20:59.460: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:20:59.460: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:59.460: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:20:59.460: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:20:59.460: INFO: 
  Jan 16 17:21:01.462: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:01.462: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:01.462: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:01.462: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
  Jan 16 17:21:01.462: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:01.462: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:01.462: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:01.462: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:01.462: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:01.462: INFO: 
  Jan 16 17:21:03.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:03.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:03.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:03.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
  Jan 16 17:21:03.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:03.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:03.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:03.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:03.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:03.458: INFO: 
  Jan 16 17:21:05.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:05.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:05.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:05.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
  Jan 16 17:21:05.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:05.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:05.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:05.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:05.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:05.458: INFO: 
  Jan 16 17:21:07.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:07.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:07.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:07.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
  Jan 16 17:21:07.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:07.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:07.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:07.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:07.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:07.455: INFO: 
  Jan 16 17:21:09.468: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:09.468: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:09.468: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:09.468: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
  Jan 16 17:21:09.468: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:09.468: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:09.468: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:09.468: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:09.468: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:09.468: INFO: 
  Jan 16 17:21:11.466: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:11.466: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:11.466: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:11.466: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
  Jan 16 17:21:11.466: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:11.466: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:11.466: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:11.466: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:11.466: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:11.466: INFO: 
  Jan 16 17:21:13.463: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:13.463: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:13.463: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:13.463: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
  Jan 16 17:21:13.463: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:13.463: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:13.463: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:13.463: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:13.463: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:13.463: INFO: 
  Jan 16 17:21:15.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:15.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:15.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:15.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
  Jan 16 17:21:15.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:15.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:15.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:15.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:15.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:15.457: INFO: 
  Jan 16 17:21:17.460: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:17.460: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:17.460: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:17.460: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
  Jan 16 17:21:17.460: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:17.460: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:17.460: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:17.460: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:17.460: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:17.460: INFO: 
  Jan 16 17:21:19.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:19.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:19.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:19.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
  Jan 16 17:21:19.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:19.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:19.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:19.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:19.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:19.459: INFO: 
  Jan 16 17:21:21.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:21.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:21.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:21.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
  Jan 16 17:21:21.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:21.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:21.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:21.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:21.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:21.457: INFO: 
  Jan 16 17:21:23.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:23.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:23.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:23.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
  Jan 16 17:21:23.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:23.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:23.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:23.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:23.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:23.456: INFO: 
  Jan 16 17:21:25.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:25.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:25.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:25.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
  Jan 16 17:21:25.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:25.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:25.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:25.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:25.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:25.457: INFO: 
  Jan 16 17:21:27.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:27.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:27.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:27.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
  Jan 16 17:21:27.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:27.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:27.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:27.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:27.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:27.457: INFO: 
  Jan 16 17:21:29.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:29.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:29.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:29.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
  Jan 16 17:21:29.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:29.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:29.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:29.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:29.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:29.458: INFO: 
  Jan 16 17:21:31.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:31.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:31.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:31.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
  Jan 16 17:21:31.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:31.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:31.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:31.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:31.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:31.457: INFO: 
  Jan 16 17:21:33.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:33.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:33.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:33.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
  Jan 16 17:21:33.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:33.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:33.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:33.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:33.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:33.458: INFO: 
  Jan 16 17:21:35.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:35.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:35.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:35.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
  Jan 16 17:21:35.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:35.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:35.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:35.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:35.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:35.457: INFO: 
  Jan 16 17:21:37.462: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:37.462: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:37.462: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:37.462: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
  Jan 16 17:21:37.462: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:37.462: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:37.462: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:37.462: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:37.462: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:37.462: INFO: 
  Jan 16 17:21:39.460: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:39.460: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:39.460: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:39.460: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
  Jan 16 17:21:39.460: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:39.460: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:39.460: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:39.460: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:39.460: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:39.460: INFO: 
  Jan 16 17:21:41.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:41.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:41.460: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:41.460: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
  Jan 16 17:21:41.460: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:41.460: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:41.460: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:41.460: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:41.460: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:41.460: INFO: 
  Jan 16 17:21:43.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:43.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:43.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:43.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
  Jan 16 17:21:43.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:43.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:43.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:43.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:43.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:43.456: INFO: 
  Jan 16 17:21:45.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:45.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:45.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:45.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
  Jan 16 17:21:45.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:45.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:45.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:45.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:45.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:45.458: INFO: 
  Jan 16 17:21:47.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:47.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:47.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:47.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
  Jan 16 17:21:47.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:47.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:47.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:47.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:47.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:47.458: INFO: 
  Jan 16 17:21:49.462: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:49.462: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:49.462: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:49.462: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
  Jan 16 17:21:49.462: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:49.462: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:49.462: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:49.462: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:49.462: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:49.462: INFO: 
  Jan 16 17:21:51.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:51.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:51.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:51.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
  Jan 16 17:21:51.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:51.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:51.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:51.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:51.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:51.457: INFO: 
  Jan 16 17:21:53.461: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:53.461: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:53.461: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:53.461: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
  Jan 16 17:21:53.461: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:53.461: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:53.461: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:53.461: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:53.461: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:53.461: INFO: 
  Jan 16 17:21:55.460: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:55.460: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:55.460: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:55.460: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
  Jan 16 17:21:55.460: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:55.460: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:55.461: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:55.461: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:55.461: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:55.461: INFO: 
  Jan 16 17:21:57.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:57.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:57.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:57.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
  Jan 16 17:21:57.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:57.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:57.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:57.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:57.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:57.459: INFO: 
  Jan 16 17:21:59.465: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:59.465: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:59.465: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:21:59.465: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
  Jan 16 17:21:59.465: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:21:59.465: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:21:59.465: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:59.465: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:21:59.465: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:21:59.465: INFO: 
  Jan 16 17:22:01.462: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:01.462: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:01.462: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:01.462: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
  Jan 16 17:22:01.462: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:01.462: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:01.462: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:01.462: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:01.462: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:01.462: INFO: 
  Jan 16 17:22:03.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:03.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:03.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:03.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
  Jan 16 17:22:03.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:03.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:03.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:03.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:03.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:03.457: INFO: 
  Jan 16 17:22:05.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:05.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:05.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:05.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
  Jan 16 17:22:05.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:05.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:05.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:05.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:05.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:05.459: INFO: 
  Jan 16 17:22:07.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:07.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:07.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:07.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
  Jan 16 17:22:07.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:07.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:07.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:07.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:07.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:07.456: INFO: 
  Jan 16 17:22:09.461: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:09.461: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:09.461: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:09.461: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
  Jan 16 17:22:09.461: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:09.461: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:09.461: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:09.461: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:09.461: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:09.461: INFO: 
  Jan 16 17:22:11.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:11.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:11.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:11.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
  Jan 16 17:22:11.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:11.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:11.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:11.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:11.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:11.458: INFO: 
  Jan 16 17:22:13.461: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:13.461: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:13.461: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:13.461: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
  Jan 16 17:22:13.461: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:13.461: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:13.461: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:13.461: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:13.461: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:13.461: INFO: 
  Jan 16 17:22:15.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:15.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:15.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:15.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
  Jan 16 17:22:15.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:15.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:15.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:15.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:15.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:15.454: INFO: 
  Jan 16 17:22:17.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:17.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:17.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:17.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
  Jan 16 17:22:17.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:17.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:17.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:17.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:17.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:17.458: INFO: 
  Jan 16 17:22:19.474: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:19.474: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:19.474: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:19.474: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
  Jan 16 17:22:19.474: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:19.474: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:19.474: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:19.474: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:19.474: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:19.474: INFO: 
  Jan 16 17:22:21.461: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:21.461: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:21.461: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:21.461: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
  Jan 16 17:22:21.461: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:21.461: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:21.461: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:21.461: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:21.461: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:21.461: INFO: 
  Jan 16 17:22:23.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:23.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:23.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:23.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
  Jan 16 17:22:23.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:23.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:23.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:23.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:23.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:23.454: INFO: 
  Jan 16 17:22:25.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:25.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:25.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:25.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
  Jan 16 17:22:25.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:25.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:25.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:25.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:25.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:25.455: INFO: 
  Jan 16 17:22:27.462: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:27.462: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:27.462: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:27.462: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
  Jan 16 17:22:27.462: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:27.462: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:27.462: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:27.462: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:27.462: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:27.462: INFO: 
  Jan 16 17:22:29.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:29.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:29.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:29.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
  Jan 16 17:22:29.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:29.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:29.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:29.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:29.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:29.458: INFO: 
  Jan 16 17:22:31.462: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:31.462: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:31.462: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:31.462: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
  Jan 16 17:22:31.462: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:31.462: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:31.462: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:31.462: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:31.462: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:31.462: INFO: 
  Jan 16 17:22:33.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:33.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:33.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:33.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
  Jan 16 17:22:33.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:33.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:33.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:33.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:33.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:33.457: INFO: 
  Jan 16 17:22:35.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:35.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:35.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:35.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
  Jan 16 17:22:35.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:35.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:35.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:35.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:35.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:35.455: INFO: 
  Jan 16 17:22:37.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:37.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:37.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:37.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
  Jan 16 17:22:37.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:37.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:37.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:37.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:37.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:37.459: INFO: 
  Jan 16 17:22:39.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:39.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:39.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:39.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
  Jan 16 17:22:39.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:39.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:39.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:39.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:39.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:39.456: INFO: 
  Jan 16 17:22:41.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:41.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:41.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:41.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
  Jan 16 17:22:41.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:41.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:41.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:41.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:41.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:41.459: INFO: 
  Jan 16 17:22:43.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:43.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:43.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:43.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
  Jan 16 17:22:43.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:43.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:43.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:43.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:43.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:43.457: INFO: 
  Jan 16 17:22:45.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:45.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:45.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:45.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
  Jan 16 17:22:45.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:45.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:45.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:45.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:45.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:45.457: INFO: 
  Jan 16 17:22:47.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:47.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:47.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:47.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
  Jan 16 17:22:47.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:47.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:47.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:47.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:47.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:47.457: INFO: 
  Jan 16 17:22:49.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:49.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:49.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:49.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
  Jan 16 17:22:49.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:49.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:49.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:49.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:49.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:49.455: INFO: 
  Jan 16 17:22:51.462: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:51.462: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:51.462: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:51.462: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
  Jan 16 17:22:51.462: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:51.462: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:51.462: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:51.462: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:51.462: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:51.462: INFO: 
  Jan 16 17:22:53.465: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:53.465: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:53.465: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:53.465: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
  Jan 16 17:22:53.465: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:53.465: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:53.465: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:53.465: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:53.465: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:53.465: INFO: 
  Jan 16 17:22:55.462: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:55.462: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:55.462: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:55.462: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
  Jan 16 17:22:55.462: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:55.462: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:55.462: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:55.462: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:55.462: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:55.462: INFO: 
  Jan 16 17:22:57.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:57.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:57.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:57.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
  Jan 16 17:22:57.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:57.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:57.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:57.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:57.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:57.459: INFO: 
  Jan 16 17:22:59.478: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:59.478: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:59.478: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:22:59.478: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
  Jan 16 17:22:59.478: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:22:59.478: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:22:59.478: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:59.478: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:22:59.478: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:22:59.478: INFO: 
  Jan 16 17:23:01.460: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:01.460: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:01.460: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:01.460: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
  Jan 16 17:23:01.460: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:01.460: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:01.460: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:01.460: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:01.460: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:01.460: INFO: 
  Jan 16 17:23:03.463: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:03.463: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:03.463: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:03.463: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
  Jan 16 17:23:03.463: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:03.463: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:03.463: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:03.463: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:03.463: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:03.463: INFO: 
  Jan 16 17:23:05.461: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:05.461: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:05.461: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:05.461: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
  Jan 16 17:23:05.461: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:05.461: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:05.461: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:05.461: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:05.461: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:05.461: INFO: 
  Jan 16 17:23:07.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:07.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:07.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:07.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
  Jan 16 17:23:07.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:07.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:07.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:07.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:07.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:07.459: INFO: 
  Jan 16 17:23:09.460: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:09.460: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:09.460: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:09.460: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
  Jan 16 17:23:09.460: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:09.460: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:09.460: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:09.460: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:09.460: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:09.460: INFO: 
  Jan 16 17:23:11.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:11.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:11.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:11.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
  Jan 16 17:23:11.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:11.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:11.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:11.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:11.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:11.459: INFO: 
  Jan 16 17:23:13.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:13.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:13.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:13.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
  Jan 16 17:23:13.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:13.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:13.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:13.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:13.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:13.457: INFO: 
  Jan 16 17:23:15.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:15.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:15.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:15.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
  Jan 16 17:23:15.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:15.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:15.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:15.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:15.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:15.454: INFO: 
  Jan 16 17:23:17.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:17.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:17.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:17.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
  Jan 16 17:23:17.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:17.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:17.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:17.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:17.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:17.458: INFO: 
  Jan 16 17:23:19.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:19.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:19.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:19.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
  Jan 16 17:23:19.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:19.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:19.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:19.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:19.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:19.458: INFO: 
  Jan 16 17:23:21.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:21.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:21.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:21.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
  Jan 16 17:23:21.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:21.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:21.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:21.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:21.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:21.458: INFO: 
  Jan 16 17:23:23.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:23.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:23.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:23.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
  Jan 16 17:23:23.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:23.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:23.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:23.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:23.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:23.456: INFO: 
  Jan 16 17:23:25.461: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:25.461: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:25.461: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:25.461: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
  Jan 16 17:23:25.461: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:25.461: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:25.461: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:25.461: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:25.461: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:25.461: INFO: 
  Jan 16 17:23:27.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:27.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:27.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:27.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
  Jan 16 17:23:27.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:27.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:27.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:27.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:27.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:27.457: INFO: 
  Jan 16 17:23:29.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:29.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:29.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:29.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
  Jan 16 17:23:29.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:29.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:29.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:29.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:29.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:29.458: INFO: 
  Jan 16 17:23:31.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:31.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:31.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:31.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
  Jan 16 17:23:31.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:31.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:31.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:31.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:31.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:31.460: INFO: 
  Jan 16 17:23:33.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:33.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:33.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:33.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
  Jan 16 17:23:33.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:33.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:33.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:33.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:33.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:33.458: INFO: 
  Jan 16 17:23:35.460: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:35.460: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:35.460: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:35.460: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
  Jan 16 17:23:35.460: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:35.460: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:35.460: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:35.460: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:35.460: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:35.460: INFO: 
  Jan 16 17:23:37.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:37.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:37.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:37.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
  Jan 16 17:23:37.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:37.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:37.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:37.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:37.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:37.457: INFO: 
  Jan 16 17:23:39.470: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:39.470: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:39.470: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:39.470: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
  Jan 16 17:23:39.470: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:39.470: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:39.470: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:39.470: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:39.470: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:39.470: INFO: 
  Jan 16 17:23:41.460: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:41.460: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:41.460: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:41.460: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
  Jan 16 17:23:41.460: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:41.460: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:41.460: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:41.460: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:41.460: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:41.460: INFO: 
  Jan 16 17:23:43.460: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:43.460: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:43.460: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:43.460: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
  Jan 16 17:23:43.460: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:43.460: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:43.460: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:43.460: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:43.460: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:43.460: INFO: 
  Jan 16 17:23:45.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:45.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:45.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:45.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
  Jan 16 17:23:45.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:45.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:45.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:45.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:45.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:45.458: INFO: 
  Jan 16 17:23:47.461: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:47.461: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:47.461: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:47.461: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
  Jan 16 17:23:47.461: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:47.461: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:47.461: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:47.461: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:47.461: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:47.461: INFO: 
  Jan 16 17:23:49.463: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:49.463: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:49.463: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:49.463: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
  Jan 16 17:23:49.463: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:49.463: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:49.463: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:49.463: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:49.463: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:49.463: INFO: 
  Jan 16 17:23:51.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:51.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:51.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:51.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
  Jan 16 17:23:51.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:51.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:51.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:51.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:51.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:51.458: INFO: 
  Jan 16 17:23:53.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:53.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:53.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:53.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
  Jan 16 17:23:53.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:53.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:53.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:53.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:53.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:53.458: INFO: 
  Jan 16 17:23:53.586: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:53.586: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:53.586: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
  Jan 16 17:23:53.586: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
  Jan 16 17:23:53.586: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
  Jan 16 17:23:53.586: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:53.586: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:53.586: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:53.586: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:53.586: INFO: 
  �[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m@ 01/16/23 17:23:53.586�[0m
  �[1mSTEP:�[0m Found 121 events. �[38;5;243m@ 01/16/23 17:23:53.644�[0m
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:10:36 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-vmxw18-control-plane-kxjwf_ccc31be8-fabd-4df4-bb62-1c4c057e8fdf became leader
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:10:37 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-vmxw18-control-plane-kxjwf_737813e5-70c3-42bd-99d7-3db65460894f became leader
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:10:41 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-56f4c55bf9 to 2
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:10:41 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-sgp4s
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:10:41 +0000 UTC - event for coredns-56f4c55bf9: {replicaset-controller } SuccessfulCreate: Created pod: coredns-56f4c55bf9-kflz4
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:10:41 +0000 UTC - event for coredns-56f4c55bf9-kflz4: {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 16 17:23:53.645: INFO: At 2023-01-16 17:10:41 +0000 UTC - event for coredns-56f4c55bf9-sgp4s: {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 16 17:23:53.645: INFO: At 2023-01-16 17:10:41 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-g6257
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:10:41 +0000 UTC - event for kube-proxy-g6257: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-g6257 to capz-conf-vmxw18-control-plane-kxjwf
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:10:42 +0000 UTC - event for kube-proxy-g6257: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_d9497132775a68"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:10:43 +0000 UTC - event for kube-proxy-g6257: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Created: Created container kube-proxy
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:10:43 +0000 UTC - event for kube-proxy-g6257: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_d9497132775a68" in 1.601623085s (1.601713993s including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:10:44 +0000 UTC - event for kube-proxy-g6257: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Started: Started container kube-proxy
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:07 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:08 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-2hxlf
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:08 +0000 UTC - event for metrics-server-c9574f845-2hxlf: {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 16 17:23:53.645: INFO: At 2023-01-16 17:11:16 +0000 UTC - event for coredns-56f4c55bf9-kflz4: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-kflz4 to capz-conf-vmxw18-control-plane-kxjwf
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:16 +0000 UTC - event for coredns-56f4c55bf9-sgp4s: {kubelet capz-conf-vmxw18-control-plane-kxjwf} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "29509fa6d1c822d179a537781fd8a79e83bd95ab00f25ad5f14a1a2ed5b49c8c": 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 16 17:23:53.645: INFO: At 2023-01-16 17:11:16 +0000 UTC - event for coredns-56f4c55bf9-sgp4s: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-56f4c55bf9-sgp4s to capz-conf-vmxw18-control-plane-kxjwf
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:16 +0000 UTC - event for metrics-server-c9574f845-2hxlf: {kubelet capz-conf-vmxw18-control-plane-kxjwf} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "cda5689600f209e7c18791c7597befbea6205df955dc15b313cae49ccaffa387": 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 16 17:23:53.645: INFO: At 2023-01-16 17:11:16 +0000 UTC - event for metrics-server-c9574f845-2hxlf: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-2hxlf to capz-conf-vmxw18-control-plane-kxjwf
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:19 +0000 UTC - event for coredns-56f4c55bf9-kflz4: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-56f4c55bf9-kflz4
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:19 +0000 UTC - event for coredns-56f4c55bf9-sgp4s: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/coredns-56f4c55bf9-sgp4s
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:19 +0000 UTC - event for metrics-server-c9574f845-2hxlf: {taint-controller } TaintManagerEviction: Cancelling deletion of Pod kube-system/metrics-server-c9574f845-2hxlf
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:20 +0000 UTC - event for coredns-56f4c55bf9-kflz4: {kubelet capz-conf-vmxw18-control-plane-kxjwf} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "4ff3ac3ac7ac670e2bcc1a583c85ed1b923a3a1647bbe891b518dcb0593d0584": 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 16 17:23:53.645: INFO: At 2023-01-16 17:11:28 +0000 UTC - event for metrics-server-c9574f845-2hxlf: {kubelet capz-conf-vmxw18-control-plane-kxjwf} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "1bfe44a132676ccee9ed94db6271d654830c1a22c7ae9205e2c7ce7710b677bb": 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 16 17:23:53.645: INFO: At 2023-01-16 17:11:32 +0000 UTC - event for coredns-56f4c55bf9-sgp4s: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Started: Started container coredns
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:32 +0000 UTC - event for coredns-56f4c55bf9-sgp4s: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Created: Created container coredns
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:32 +0000 UTC - event for coredns-56f4c55bf9-sgp4s: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:39 +0000 UTC - event for coredns-56f4c55bf9-kflz4: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.10.0" already present on machine
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:39 +0000 UTC - event for coredns-56f4c55bf9-kflz4: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Created: Created container coredns
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:40 +0000 UTC - event for coredns-56f4c55bf9-kflz4: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Started: Started container coredns
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:40 +0000 UTC - event for metrics-server-c9574f845-2hxlf: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:49 +0000 UTC - event for metrics-server-c9574f845-2hxlf: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Started: Started container metrics-server
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:49 +0000 UTC - event for metrics-server-c9574f845-2hxlf: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Created: Created container metrics-server
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:11:49 +0000 UTC - event for metrics-server-c9574f845-2hxlf: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 3.767049418s (9.15997057s including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:08 +0000 UTC - event for csi-azuredisk-controller: {deployment-controller } ScalingReplicaSet: Scaled up replica set csi-azuredisk-controller-7c87ff77db to 1
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:08 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db: {replicaset-controller } SuccessfulCreate: Created pod: csi-azuredisk-controller-7c87ff77db-6868l
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:08 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-controller-7c87ff77db-6868l to capz-conf-vmxw18-control-plane-kxjwf
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:08 +0000 UTC - event for csi-azuredisk-node: {daemonset-controller } SuccessfulCreate: Created pod: csi-azuredisk-node-kw4f7
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:08 +0000 UTC - event for csi-azuredisk-node-kw4f7: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-node-kw4f7 to capz-conf-vmxw18-control-plane-kxjwf
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:09 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner:v3.3.0"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:09 +0000 UTC - event for csi-azuredisk-node-kw4f7: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:10 +0000 UTC - event for csi-azuredisk-node-kw4f7: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" in 901.082957ms (901.165158ms including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:10 +0000 UTC - event for csi-azuredisk-node-kw4f7: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Created: Created container liveness-probe
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:10 +0000 UTC - event for csi-azuredisk-node-kw4f7: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Started: Started container liveness-probe
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:10 +0000 UTC - event for csi-azuredisk-node-kw4f7: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:13 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner:v3.3.0" in 3.126733817s (3.943478574s including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:13 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-attacher:v4.0.0"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:13 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Created: Created container csi-provisioner
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:13 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Started: Started container csi-provisioner
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:15 +0000 UTC - event for csi-azuredisk-node-kw4f7: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" in 2.057791065s (4.972792574s including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:15 +0000 UTC - event for csi-azuredisk-node-kw4f7: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:15 +0000 UTC - event for csi-azuredisk-node-kw4f7: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Started: Started container node-driver-registrar
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:15 +0000 UTC - event for csi-azuredisk-node-kw4f7: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Created: Created container node-driver-registrar
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:17 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-attacher:v4.0.0" in 2.346357302s (4.143598726s including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:17 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Created: Created container csi-attacher
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:17 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Started: Started container csi-attacher
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:17 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter:v5.0.1"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:31 +0000 UTC - event for csi-azuredisk-node-kw4f7: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" in 14.180571703s (16.323020696s including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:33 +0000 UTC - event for csi-azuredisk-node-kw4f7: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Created: Created container azuredisk
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:33 +0000 UTC - event for csi-azuredisk-node-kw4f7: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Started: Started container azuredisk
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:35 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.6.0"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:35 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Started: Started container csi-snapshotter
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:35 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter:v5.0.1" in 3.547032571s (17.538948164s including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:35 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Created: Created container csi-snapshotter
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:39 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulled: Container image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" already present on machine
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:39 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.6.0" in 3.484284698s (3.484299898s including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:39 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Created: Created container csi-resizer
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:39 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Started: Started container csi-resizer
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:39 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Created: Created container liveness-probe
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:39 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Started: Started container liveness-probe
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:39 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Pulled: Container image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" already present on machine
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:39 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Created: Created container azuredisk
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:39 +0000 UTC - event for csi-azuredisk-controller-7c87ff77db-6868l: {kubelet capz-conf-vmxw18-control-plane-kxjwf} Started: Started container azuredisk
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:40 +0000 UTC - event for disk-csi-azure-com: {disk.csi.azure.com/1673889160011-8081-disk.csi.azure.com } LeaderElection: 1673889160011-8081-disk-csi-azure-com became leader
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:40 +0000 UTC - event for external-attacher-leader-disk-csi-azure-com: {external-attacher-leader-disk.csi.azure.com/capz-conf-vmxw18-control-plane-kxjwf } LeaderElection: capz-conf-vmxw18-control-plane-kxjwf became leader
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:40 +0000 UTC - event for external-resizer-disk-csi-azure-com: {external-resizer-disk-csi-azure-com/capz-conf-vmxw18-control-plane-kxjwf } LeaderElection: capz-conf-vmxw18-control-plane-kxjwf became leader
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:40 +0000 UTC - event for external-snapshotter-leader-disk-csi-azure-com: {external-snapshotter-leader-disk.csi.azure.com/capz-conf-vmxw18-control-plane-kxjwf } LeaderElection: capz-conf-vmxw18-control-plane-kxjwf became leader
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:40 +0000 UTC - event for kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf: {kubelet capz-conf-vmxw18-control-plane-kxjwf} FailedMount: Unable to attach or mount volumes: unmounted volumes=[k8s-certs usr-local-share-ca-certificates usr-share-ca-certificates ca-certs cloud-config etc-ca-certificates], unattached volumes=[], failed to process volumes=[ca-certs cloud-config etc-ca-certificates k8s-certs usr-local-share-ca-certificates usr-share-ca-certificates]: timed out waiting for the condition
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:54 +0000 UTC - event for csi-azuredisk-node: {daemonset-controller } SuccessfulCreate: Created pod: csi-azuredisk-node-w4jmz
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:54 +0000 UTC - event for csi-azuredisk-node-w4jmz: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-node-w4jmz to capz-conf-vmxw18-md-0-chndb
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:54 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-gk5hh
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:54 +0000 UTC - event for kube-proxy-gk5hh: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-gk5hh to capz-conf-vmxw18-md-0-chndb
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:56 +0000 UTC - event for csi-azuredisk-node: {daemonset-controller } SuccessfulCreate: Created pod: csi-azuredisk-node-pkv8r
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:56 +0000 UTC - event for csi-azuredisk-node-pkv8r: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-azuredisk-node-pkv8r to capz-conf-vmxw18-md-0-2zlxc
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:56 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-snp29
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:12:56 +0000 UTC - event for kube-proxy-snp29: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-snp29 to capz-conf-vmxw18-md-0-2zlxc
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:03 +0000 UTC - event for csi-azuredisk-node-pkv8r: {kubelet capz-conf-vmxw18-md-0-2zlxc} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:03 +0000 UTC - event for csi-azuredisk-node-w4jmz: {kubelet capz-conf-vmxw18-md-0-chndb} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:03 +0000 UTC - event for kube-proxy-gk5hh: {kubelet capz-conf-vmxw18-md-0-chndb} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_d9497132775a68"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:04 +0000 UTC - event for csi-azuredisk-node-pkv8r: {kubelet capz-conf-vmxw18-md-0-2zlxc} Created: Created container liveness-probe
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:04 +0000 UTC - event for csi-azuredisk-node-pkv8r: {kubelet capz-conf-vmxw18-md-0-2zlxc} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" in 847.531097ms (847.614998ms including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:04 +0000 UTC - event for kube-proxy-snp29: {kubelet capz-conf-vmxw18-md-0-2zlxc} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_d9497132775a68"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:05 +0000 UTC - event for csi-azuredisk-node-pkv8r: {kubelet capz-conf-vmxw18-md-0-2zlxc} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:05 +0000 UTC - event for csi-azuredisk-node-pkv8r: {kubelet capz-conf-vmxw18-md-0-2zlxc} Started: Started container liveness-probe
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:06 +0000 UTC - event for kube-proxy-snp29: {kubelet capz-conf-vmxw18-md-0-2zlxc} Created: Created container kube-proxy
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:06 +0000 UTC - event for kube-proxy-snp29: {kubelet capz-conf-vmxw18-md-0-2zlxc} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_d9497132775a68" in 1.406836736s (2.240010686s including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:06 +0000 UTC - event for kube-proxy-snp29: {kubelet capz-conf-vmxw18-md-0-2zlxc} Started: Started container kube-proxy
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:08 +0000 UTC - event for kube-proxy-gk5hh: {kubelet capz-conf-vmxw18-md-0-chndb} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_d9497132775a68" in 2.671906124s (4.711083785s including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:08 +0000 UTC - event for kube-proxy-gk5hh: {kubelet capz-conf-vmxw18-md-0-chndb} Created: Created container kube-proxy
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:08 +0000 UTC - event for kube-proxy-gk5hh: {kubelet capz-conf-vmxw18-md-0-chndb} Started: Started container kube-proxy
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:09 +0000 UTC - event for csi-azuredisk-node-w4jmz: {kubelet capz-conf-vmxw18-md-0-chndb} Created: Created container liveness-probe
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:09 +0000 UTC - event for csi-azuredisk-node-w4jmz: {kubelet capz-conf-vmxw18-md-0-chndb} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0" in 883.030123ms (5.589375227s including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:09 +0000 UTC - event for csi-azuredisk-node-w4jmz: {kubelet capz-conf-vmxw18-md-0-chndb} Started: Started container liveness-probe
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:09 +0000 UTC - event for csi-azuredisk-node-w4jmz: {kubelet capz-conf-vmxw18-md-0-chndb} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:14 +0000 UTC - event for csi-azuredisk-node-pkv8r: {kubelet capz-conf-vmxw18-md-0-2zlxc} Created: Created container node-driver-registrar
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:14 +0000 UTC - event for csi-azuredisk-node-pkv8r: {kubelet capz-conf-vmxw18-md-0-2zlxc} Started: Started container node-driver-registrar
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:14 +0000 UTC - event for csi-azuredisk-node-pkv8r: {kubelet capz-conf-vmxw18-md-0-2zlxc} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:14 +0000 UTC - event for csi-azuredisk-node-pkv8r: {kubelet capz-conf-vmxw18-md-0-2zlxc} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" in 909.595862ms (9.631867953s including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:20 +0000 UTC - event for csi-azuredisk-node-w4jmz: {kubelet capz-conf-vmxw18-md-0-chndb} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2" in 6.266892879s (11.118645124s including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:22 +0000 UTC - event for csi-azuredisk-node-w4jmz: {kubelet capz-conf-vmxw18-md-0-chndb} Created: Created container node-driver-registrar
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:22 +0000 UTC - event for csi-azuredisk-node-w4jmz: {kubelet capz-conf-vmxw18-md-0-chndb} Started: Started container node-driver-registrar
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:22 +0000 UTC - event for csi-azuredisk-node-w4jmz: {kubelet capz-conf-vmxw18-md-0-chndb} Pulling: Pulling image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1"
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:37 +0000 UTC - event for csi-azuredisk-node-w4jmz: {kubelet capz-conf-vmxw18-md-0-chndb} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" in 15.192715723s (15.192793801s including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:37 +0000 UTC - event for csi-azuredisk-node-w4jmz: {kubelet capz-conf-vmxw18-md-0-chndb} Created: Created container azuredisk
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:37 +0000 UTC - event for csi-azuredisk-node-w4jmz: {kubelet capz-conf-vmxw18-md-0-chndb} Started: Started container azuredisk
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:43 +0000 UTC - event for csi-azuredisk-node-pkv8r: {kubelet capz-conf-vmxw18-md-0-2zlxc} Started: Started container azuredisk
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:43 +0000 UTC - event for csi-azuredisk-node-pkv8r: {kubelet capz-conf-vmxw18-md-0-2zlxc} Created: Created container azuredisk
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:13:43 +0000 UTC - event for csi-azuredisk-node-pkv8r: {kubelet capz-conf-vmxw18-md-0-2zlxc} Pulled: Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1" in 22.441993271s (28.244823629s including waiting)
  Jan 16 17:23:53.645: INFO: At 2023-01-16 17:14:43 +0000 UTC - event for kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf: {kubelet capz-conf-vmxw18-control-plane-kxjwf} FailedMount: Unable to attach or mount volumes: unmounted volumes=[etc-ca-certificates k8s-certs usr-local-share-ca-certificates usr-share-ca-certificates ca-certs cloud-config], unattached volumes=[], failed to process volumes=[ca-certs cloud-config etc-ca-certificates k8s-certs usr-local-share-ca-certificates usr-share-ca-certificates]: timed out waiting for the condition
  Jan 16 17:23:53.699: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
  Jan 16 17:23:53.699: INFO: coredns-56f4c55bf9-kflz4                                      capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:11:16 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:11:41 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:11:41 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:11:15 +0000 UTC  }]
  Jan 16 17:23:53.699: INFO: coredns-56f4c55bf9-sgp4s                                      capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:11:16 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:11:33 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:11:33 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:11:15 +0000 UTC  }]
  Jan 16 17:23:53.699: INFO: csi-azuredisk-controller-7c87ff77db-6868l                     capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:12:08 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:12:40 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:12:40 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:12:08 +0000 UTC  }]
  Jan 16 17:23:53.699: INFO: csi-azuredisk-node-kw4f7                                      capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:12:08 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:12:34 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:12:34 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:12:08 +0000 UTC  }]
  Jan 16 17:23:53.699: INFO: csi-azuredisk-node-pkv8r                                      capz-conf-vmxw18-md-0-2zlxc           Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:12:59 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:13:43 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:13:43 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:12:56 +0000 UTC  }]
  Jan 16 17:23:53.699: INFO: csi-azuredisk-node-w4jmz                                      capz-conf-vmxw18-md-0-chndb           Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:13:00 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:13:38 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:13:38 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:12:54 +0000 UTC  }]
  Jan 16 17:23:53.699: INFO: etcd-capz-conf-vmxw18-control-plane-kxjwf                     capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:37 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:44 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:44 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:37 +0000 UTC  }]
  Jan 16 17:23:53.699: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:53.699: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
  Jan 16 17:23:53.699: INFO: kube-proxy-g6257                                              capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:41 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:44 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:44 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:41 +0000 UTC  }]
  Jan 16 17:23:53.699: INFO: kube-proxy-gk5hh                                              capz-conf-vmxw18-md-0-chndb           Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:13:00 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:13:09 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:13:09 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:12:54 +0000 UTC  }]
  Jan 16 17:23:53.699: INFO: kube-proxy-snp29                                              capz-conf-vmxw18-md-0-2zlxc           Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:12:59 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:13:06 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:13:06 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:12:56 +0000 UTC  }]
  Jan 16 17:23:53.699: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
  Jan 16 17:23:53.699: INFO: metrics-server-c9574f845-2hxlf                                capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:11:16 +0000 UTC  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:12:16 +0000 UTC  } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:12:16 +0000 UTC  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:11:15 +0000 UTC  }]
  Jan 16 17:23:53.699: INFO: 
  Jan 16 17:23:55.573: INFO: 
  Logging node info for node capz-conf-vmxw18-control-plane-kxjwf
  Jan 16 17:23:55.772: INFO: Node Info: &Node{ObjectMeta:{capz-conf-vmxw18-control-plane-kxjwf    631704a8-f4d1-4697-84ba-9c9d0852c275 3169 0 2023-01-16 17:10:33 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_B2s beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:eastus failure-domain.beta.kubernetes.io/zone:eastus-1 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-vmxw18-control-plane-kxjwf kubernetes.io/os:linux node-role.kubernetes.io/control-plane: node.kubernetes.io/exclude-from-external-load-balancers: node.kubernetes.io/instance-type:Standard_B2s topology.disk.csi.azure.com/zone:eastus-1 topology.kubernetes.io/region:eastus topology.kubernetes.io/zone:eastus-1] map[cluster.x-k8s.io/cluster-name:capz-conf-vmxw18 cluster.x-k8s.io/cluster-namespace:capz-conf-vmxw18 cluster.x-k8s.io/machine:capz-conf-vmxw18-control-plane-tcdk6 cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-vmxw18-control-plane csi.volume.kubernetes.io/nodeid:{"csi.tigera.io":"capz-conf-vmxw18-control-plane-kxjwf","disk.csi.azure.com":"capz-conf-vmxw18-control-plane-kxjwf"} 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.145.64 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-16 17:10:33 +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-16 17:10:36 +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-16 17:11:06 +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-16 17:11:16 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {calico-node Update v1 2023-01-16 17:11:30 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2023-01-16 17:23:21 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.disk.csi.azure.com/zone":{}}},"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-vmxw18/providers/Microsoft.Compute/virtualMachines/capz-conf-vmxw18-control-plane-kxjwf,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/control-plane,Value:,Effect:NoSchedule,TimeAdded:<nil>,},},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{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: {{4123181056 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{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: {{4018323456 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-16 17:11:30 +0000 UTC,LastTransitionTime:2023-01-16 17:11:30 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-16 17:23:21 +0000 UTC,LastTransitionTime:2023-01-16 17:10:15 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-16 17:23:21 +0000 UTC,LastTransitionTime:2023-01-16 17:10:15 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-16 17:23:21 +0000 UTC,LastTransitionTime:2023-01-16 17:10:15 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-16 17:23:21 +0000 UTC,LastTransitionTime:2023-01-16 17:11:15 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-vmxw18-control-plane-kxjwf,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:bad296b9baca410ea31c2e96d5c48004,SystemUUID:8ad8d59b-3c7f-a847-99ee-234d639c318e,BootID:0c67178a-42de-4a44-b362-332e14e8dcb3,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1003+d9497132775a68,KubeProxyVersion:v1.27.0-alpha.0.1003+d9497132775a68,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi@sha256:907b259fe0c9f5adda9f00a91b8a8228f4f38768021fb6d05cbad0538ef8f99a mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1],SizeBytes:96300330,},ContainerImage{Names:[docker.io/calico/cni@sha256:a38d53cb8688944eafede2f0eadc478b1b403cefeff7953da57fe9cd2d65e977 docker.io/calico/cni:v3.25.0],SizeBytes:87984941,},ContainerImage{Names:[docker.io/calico/node@sha256:a85123d1882832af6c45b5e289c6bb99820646cb7d4f6006f98095168808b1e6 docker.io/calico/node:v3.25.0],SizeBytes:87185935,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner@sha256:3ef7d954946bd1cf9e5e3564a8d1acf8e5852616f7ae96bcbc5ced8c275483ee mcr.microsoft.com/oss/kubernetes-csi/csi-provisioner:v3.3.0],SizeBytes:61391360,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-resizer@sha256:9ba6483d2f8aa6051cb3a50e42d638fc17a6e4699a6689f054969024b7c12944 mcr.microsoft.com/oss/kubernetes-csi/csi-resizer:v1.6.0],SizeBytes:58560473,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-attacher@sha256:bc317fea7e7bbaff65130d7ac6ea7c96bc15eb1f086374b8c3359f11988ac024 mcr.microsoft.com/oss/kubernetes-csi/csi-attacher:v4.0.0],SizeBytes:57948644,},ContainerImage{Names:[docker.io/calico/apiserver@sha256:9819c1b569e60eec4dbab82c1b41cee80fe8af282b25ba2c174b2a00ae555af6 docker.io/calico/apiserver:v3.25.0],SizeBytes:35624155,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-apiserver@sha256:f3d314c50fb13960970bee5c2d76f2743553d2663ef2b8e3dcce99a632b60af2 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.999_ed8cad1e80d096],SizeBytes:35446863,},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-controller-manager@sha256:907ee4f4d9eeaedd198ecb39eabce71de1bb7d5c95938423920780155ba3ad17 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.999_ed8cad1e80d096],SizeBytes:32311072,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:26e260b50ec46bd1da7352565cb8b34b6dd2cb006cebbd2f35170d50935fb9ec registry.k8s.io/kube-controller-manager:v1.26.0],SizeBytes:32244989,},ContainerImage{Names:[docker.io/calico/kube-controllers@sha256:c45af3a9692d87a527451cf544557138fedf86f92b6e39bf2003e2fdb848dce3 docker.io/calico/kube-controllers:v3.25.0],SizeBytes:31271800,},ContainerImage{Names:[docker.io/calico/typha@sha256:f7e0557e03f422c8ba5fcf64ef0fac054ee99935b5d101a0a50b5e9b65f6a5c5 docker.io/calico/typha:v3.25.0],SizeBytes:28533187,},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:[mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter@sha256:a889e925e15f9423f7842f1b769f64cbcf6a20b6956122836fc835cf22d9073f mcr.microsoft.com/oss/kubernetes-csi/csi-snapshotter:v5.0.1],SizeBytes:22192414,},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:9b04f65bb36e6f8c210f143be8a177c6025954115ccd882540ed461b3e38393b gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.999_ed8cad1e80d096],SizeBytes:21485066,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:c822ba9fa7e1a4502297347cbc1dcf37b9ec7ed5d9c8b867071a19798b2261b2 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_d9497132775a68],SizeBytes:21483039,},ContainerImage{Names:[quay.io/tigera/operator@sha256:89eef35e1bbe8c88792ce69c3f3f38fb9838e58602c570524350b5f3ab127582 quay.io/tigera/operator:v1.29.0],SizeBytes:21108896,},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:cb5fba6e65765cc93424768170c13c0a8dfe055ed8625b2276df660c562bf2d4 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.999_ed8cad1e80d096],SizeBytes:17469373,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:017727efcfeb7d053af68e51436ce8e65edbc6ca573720afb4f79c8594036955 registry.k8s.io/coredns/coredns:v1.10.0],SizeBytes:15273057,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[docker.io/calico/node-driver-registrar@sha256:f559ee53078266d2126732303f588b9d4266607088e457ea04286f31727676f7 docker.io/calico/node-driver-registrar:v3.25.0],SizeBytes:11133658,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar@sha256:515b883deb0ae8d58eef60312f4d460ff8a3f52a2a5e487c94a8ebb2ca362720 mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2],SizeBytes:10076715,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/livenessprobe@sha256:fcb73e1939d9abeb2d1e1680b476a10a422a04a73ea5a65e64eec3fde1f2a5a1 mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0],SizeBytes:9117963,},ContainerImage{Names:[docker.io/calico/csi@sha256:61a95f3ee79a7e591aff9eff535be73e62d2c3931d07c2ea8a1305f7bea19b31 docker.io/calico/csi:v3.25.0],SizeBytes:9076936,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:01ddd57d428787b3ac689daa685660defe4bd7810069544bd43a9103a7b0a789 docker.io/calico/pod2daemon-flexvol:v3.25.0],SizeBytes:7076045,},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 16 17:23:55.773: INFO: 
  Logging kubelet events for node capz-conf-vmxw18-control-plane-kxjwf
  Jan 16 17:23:55.974: INFO: 
  Logging pods the kubelet thinks is on node capz-conf-vmxw18-control-plane-kxjwf
  Jan 16 17:23:56.192: INFO: calico-typha-5dbf8c789f-tjklr started at 2023-01-16 17:10:50 +0000 UTC (0+1 container statuses recorded)
  Jan 16 17:23:56.192: INFO: 	Container calico-typha ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: coredns-56f4c55bf9-sgp4s started at 2023-01-16 17:11:16 +0000 UTC (0+1 container statuses recorded)
  Jan 16 17:23:56.192: INFO: 	Container coredns ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: coredns-56f4c55bf9-kflz4 started at 2023-01-16 17:11:16 +0000 UTC (0+1 container statuses recorded)
  Jan 16 17:23:56.192: INFO: 	Container coredns ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: calico-kube-controllers-6b7b9c649d-d649m started at 2023-01-16 17:11:16 +0000 UTC (0+1 container statuses recorded)
  Jan 16 17:23:56.192: INFO: 	Container calico-kube-controllers ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: csi-node-driver-kcrm6 started at 2023-01-16 17:11:16 +0000 UTC (0+2 container statuses recorded)
  Jan 16 17:23:56.192: INFO: 	Container calico-csi ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: 	Container csi-node-driver-registrar ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: calico-apiserver-86685f5cdf-kxmzb started at 2023-01-16 17:11:50 +0000 UTC (0+1 container statuses recorded)
  Jan 16 17:23:56.192: INFO: 	Container calico-apiserver ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: calico-apiserver-86685f5cdf-gh5z5 started at 2023-01-16 17:11:50 +0000 UTC (0+1 container statuses recorded)
  Jan 16 17:23:56.192: INFO: 	Container calico-apiserver ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf started at <nil> (0+0 container statuses recorded)
  Jan 16 17:23:56.192: INFO: csi-azuredisk-controller-7c87ff77db-6868l started at 2023-01-16 17:12:08 +0000 UTC (0+6 container statuses recorded)
  Jan 16 17:23:56.192: INFO: 	Container azuredisk ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: 	Container csi-attacher ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: 	Container csi-provisioner ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: 	Container csi-resizer ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: 	Container csi-snapshotter ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: 	Container liveness-probe ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: etcd-capz-conf-vmxw18-control-plane-kxjwf started at 2023-01-16 17:10:37 +0000 UTC (0+1 container statuses recorded)
  Jan 16 17:23:56.192: INFO: 	Container etcd ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf started at <nil> (0+0 container statuses recorded)
  Jan 16 17:23:56.192: INFO: kube-proxy-g6257 started at 2023-01-16 17:10:41 +0000 UTC (0+1 container statuses recorded)
  Jan 16 17:23:56.192: INFO: 	Container kube-proxy ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: calico-node-6sbp2 started at 2023-01-16 17:10:50 +0000 UTC (2+1 container statuses recorded)
  Jan 16 17:23:56.192: INFO: 	Init container flexvol-driver ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: 	Init container install-cni ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: 	Container calico-node ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf started at <nil> (0+0 container statuses recorded)
  Jan 16 17:23:56.192: INFO: metrics-server-c9574f845-2hxlf started at 2023-01-16 17:11:16 +0000 UTC (0+1 container statuses recorded)
  Jan 16 17:23:56.192: INFO: 	Container metrics-server ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: csi-azuredisk-node-kw4f7 started at 2023-01-16 17:12:08 +0000 UTC (0+3 container statuses recorded)
  Jan 16 17:23:56.192: INFO: 	Container azuredisk ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: 	Container liveness-probe ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: 	Container node-driver-registrar ready: true, restart count 0
  Jan 16 17:23:56.192: INFO: tigera-operator-54b47459dd-pg6mz started at 2023-01-16 17:10:42 +0000 UTC (0+1 container statuses recorded)
  Jan 16 17:23:56.192: INFO: 	Container tigera-operator ready: true, restart count 0
  Jan 16 17:23:56.849: INFO: 
  Latency metrics for node capz-conf-vmxw18-control-plane-kxjwf
  Jan 16 17:23:56.849: INFO: 
  Logging node info for node capz-conf-vmxw18-md-0-2zlxc
  Jan 16 17:23:56.971: INFO: Node Info: &Node{ObjectMeta:{capz-conf-vmxw18-md-0-2zlxc    818051c9-4957-4cd9-9fd1-8f3233e57efd 2507 0 2023-01-16 17:12:56 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_B2s beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:eastus failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-vmxw18-md-0-2zlxc kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_B2s topology.disk.csi.azure.com/zone: topology.kubernetes.io/region:eastus topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-vmxw18 cluster.x-k8s.io/cluster-namespace:capz-conf-vmxw18 cluster.x-k8s.io/machine:capz-conf-vmxw18-md-0-77f5c85f54-w7tlj cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-vmxw18-md-0-77f5c85f54 csi.volume.kubernetes.io/nodeid:{"csi.tigera.io":"capz-conf-vmxw18-md-0-2zlxc","disk.csi.azure.com":"capz-conf-vmxw18-md-0-2zlxc"} 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.146.192 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2023-01-16 17:12:56 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet Update v1 2023-01-16 17:12:56 +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-16 17:13:18 +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-16 17:13:35 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {calico-node Update v1 2023-01-16 17:13:52 +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-16 17:19:23 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.disk.csi.azure.com/zone":{}}},"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-vmxw18/providers/Microsoft.Compute/virtualMachines/capz-conf-vmxw18-md-0-2zlxc,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{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: {{4123181056 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{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: {{4018323456 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-16 17:13:52 +0000 UTC,LastTransitionTime:2023-01-16 17:13:52 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-16 17:19:23 +0000 UTC,LastTransitionTime:2023-01-16 17:12:55 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-16 17:19:23 +0000 UTC,LastTransitionTime:2023-01-16 17:12:55 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-16 17:19:23 +0000 UTC,LastTransitionTime:2023-01-16 17:12:55 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-16 17:19:23 +0000 UTC,LastTransitionTime:2023-01-16 17:13:35 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-vmxw18-md-0-2zlxc,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:d95e590c124b432da1844bc870544628,SystemUUID:c31a1b91-cbb8-a044-bcb9-ca92585f1559,BootID:16b1ec28-c89e-4e57-8bf1-a9cc176ed78f,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1003+d9497132775a68,KubeProxyVersion:v1.27.0-alpha.0.1003+d9497132775a68,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi@sha256:907b259fe0c9f5adda9f00a91b8a8228f4f38768021fb6d05cbad0538ef8f99a mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1],SizeBytes:96300330,},ContainerImage{Names:[docker.io/calico/cni@sha256:a38d53cb8688944eafede2f0eadc478b1b403cefeff7953da57fe9cd2d65e977 docker.io/calico/cni:v3.25.0],SizeBytes:87984941,},ContainerImage{Names:[docker.io/calico/node@sha256:a85123d1882832af6c45b5e289c6bb99820646cb7d4f6006f98095168808b1e6 docker.io/calico/node:v3.25.0],SizeBytes:87185935,},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:[docker.io/calico/typha@sha256:f7e0557e03f422c8ba5fcf64ef0fac054ee99935b5d101a0a50b5e9b65f6a5c5 docker.io/calico/typha:v3.25.0],SizeBytes:28533187,},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:c822ba9fa7e1a4502297347cbc1dcf37b9ec7ed5d9c8b867071a19798b2261b2 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_d9497132775a68],SizeBytes:21483039,},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:[docker.io/calico/node-driver-registrar@sha256:f559ee53078266d2126732303f588b9d4266607088e457ea04286f31727676f7 docker.io/calico/node-driver-registrar:v3.25.0],SizeBytes:11133658,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar@sha256:515b883deb0ae8d58eef60312f4d460ff8a3f52a2a5e487c94a8ebb2ca362720 mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2],SizeBytes:10076715,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/livenessprobe@sha256:fcb73e1939d9abeb2d1e1680b476a10a422a04a73ea5a65e64eec3fde1f2a5a1 mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0],SizeBytes:9117963,},ContainerImage{Names:[docker.io/calico/csi@sha256:61a95f3ee79a7e591aff9eff535be73e62d2c3931d07c2ea8a1305f7bea19b31 docker.io/calico/csi:v3.25.0],SizeBytes:9076936,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:01ddd57d428787b3ac689daa685660defe4bd7810069544bd43a9103a7b0a789 docker.io/calico/pod2daemon-flexvol:v3.25.0],SizeBytes:7076045,},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 16 17:23:56.972: INFO: 
  Logging kubelet events for node capz-conf-vmxw18-md-0-2zlxc
  Jan 16 17:23:57.173: INFO: 
  Logging pods the kubelet thinks is on node capz-conf-vmxw18-md-0-2zlxc
  Jan 16 17:23:57.387: INFO: calico-typha-5dbf8c789f-tnftc started at 2023-01-16 17:12:59 +0000 UTC (0+1 container statuses recorded)
  Jan 16 17:23:57.387: INFO: 	Container calico-typha ready: true, restart count 0
  Jan 16 17:23:57.387: INFO: csi-node-driver-6zqjc started at 2023-01-16 17:13:35 +0000 UTC (0+2 container statuses recorded)
  Jan 16 17:23:57.387: INFO: 	Container calico-csi ready: true, restart count 0
  Jan 16 17:23:57.387: INFO: 	Container csi-node-driver-registrar ready: true, restart count 0
  Jan 16 17:23:57.387: INFO: kube-proxy-snp29 started at 2023-01-16 17:12:59 +0000 UTC (0+1 container statuses recorded)
  Jan 16 17:23:57.387: INFO: 	Container kube-proxy ready: true, restart count 0
  Jan 16 17:23:57.387: INFO: calico-node-vlwbv started at 2023-01-16 17:12:59 +0000 UTC (2+1 container statuses recorded)
  Jan 16 17:23:57.387: INFO: 	Init container flexvol-driver ready: true, restart count 0
  Jan 16 17:23:57.387: INFO: 	Init container install-cni ready: true, restart count 0
  Jan 16 17:23:57.387: INFO: 	Container calico-node ready: true, restart count 0
  Jan 16 17:23:57.387: INFO: csi-azuredisk-node-pkv8r started at 2023-01-16 17:12:59 +0000 UTC (0+3 container statuses recorded)
  Jan 16 17:23:57.387: INFO: 	Container azuredisk ready: true, restart count 0
  Jan 16 17:23:57.387: INFO: 	Container liveness-probe ready: true, restart count 0
  Jan 16 17:23:57.387: INFO: 	Container node-driver-registrar ready: true, restart count 0
  Jan 16 17:23:58.012: INFO: 
  Latency metrics for node capz-conf-vmxw18-md-0-2zlxc
  Jan 16 17:23:58.012: INFO: 
  Logging node info for node capz-conf-vmxw18-md-0-chndb
  Jan 16 17:23:58.171: INFO: Node Info: &Node{ObjectMeta:{capz-conf-vmxw18-md-0-chndb    29420c95-86a6-44fd-ab08-ec0b181b6ab0 2498 0 2023-01-16 17:12:53 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_B2s beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:eastus failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-vmxw18-md-0-chndb kubernetes.io/os:linux node.kubernetes.io/instance-type:Standard_B2s topology.disk.csi.azure.com/zone: topology.kubernetes.io/region:eastus topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-vmxw18 cluster.x-k8s.io/cluster-namespace:capz-conf-vmxw18 cluster.x-k8s.io/machine:capz-conf-vmxw18-md-0-77f5c85f54-ltcp7 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-vmxw18-md-0-77f5c85f54 csi.volume.kubernetes.io/nodeid:{"csi.tigera.io":"capz-conf-vmxw18-md-0-chndb","disk.csi.azure.com":"capz-conf-vmxw18-md-0-chndb"} 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.45.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2023-01-16 17:12:53 +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-16 17:12:54 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {manager Update v1 2023-01-16 17:13:19 +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-16 17:13:22 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {calico-node Update v1 2023-01-16 17:13:50 +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-16 17:19:21 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:csi.volume.kubernetes.io/nodeid":{}},"f:labels":{"f:topology.disk.csi.azure.com/zone":{}}},"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-vmxw18/providers/Microsoft.Compute/virtualMachines/capz-conf-vmxw18-md-0-chndb,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{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: {{4123181056 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{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: {{4018323456 0} {<nil>}  BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2023-01-16 17:13:50 +0000 UTC,LastTransitionTime:2023-01-16 17:13:50 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2023-01-16 17:19:20 +0000 UTC,LastTransitionTime:2023-01-16 17:12:53 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2023-01-16 17:19:20 +0000 UTC,LastTransitionTime:2023-01-16 17:12:53 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2023-01-16 17:19:20 +0000 UTC,LastTransitionTime:2023-01-16 17:12:53 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2023-01-16 17:19:20 +0000 UTC,LastTransitionTime:2023-01-16 17:13:22 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-vmxw18-md-0-chndb,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:0e828535a91245fbbb91d9fd8730fad6,SystemUUID:bc386254-5b48-144c-a391-ed8ff65937cd,BootID:3654ee72-bd13-4aa3-af99-9c9f137f57f6,KernelVersion:5.4.0-1098-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.1003+d9497132775a68,KubeProxyVersion:v1.27.0-alpha.0.1003+d9497132775a68,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[registry.k8s.io/etcd@sha256:dd75ec974b0a2a6f6bb47001ba09207976e625db898d1b16735528c009cb171c registry.k8s.io/etcd:3.5.6-0],SizeBytes:102542580,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi@sha256:907b259fe0c9f5adda9f00a91b8a8228f4f38768021fb6d05cbad0538ef8f99a mcr.microsoft.com/oss/kubernetes-csi/azuredisk-csi:v1.26.1],SizeBytes:96300330,},ContainerImage{Names:[docker.io/calico/cni@sha256:a38d53cb8688944eafede2f0eadc478b1b403cefeff7953da57fe9cd2d65e977 docker.io/calico/cni:v3.25.0],SizeBytes:87984941,},ContainerImage{Names:[docker.io/calico/node@sha256:a85123d1882832af6c45b5e289c6bb99820646cb7d4f6006f98095168808b1e6 docker.io/calico/node:v3.25.0],SizeBytes:87185935,},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:c822ba9fa7e1a4502297347cbc1dcf37b9ec7ed5d9c8b867071a19798b2261b2 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.1003_d9497132775a68],SizeBytes:21483039,},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:[docker.io/calico/node-driver-registrar@sha256:f559ee53078266d2126732303f588b9d4266607088e457ea04286f31727676f7 docker.io/calico/node-driver-registrar:v3.25.0],SizeBytes:11133658,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar@sha256:515b883deb0ae8d58eef60312f4d460ff8a3f52a2a5e487c94a8ebb2ca362720 mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.6.2],SizeBytes:10076715,},ContainerImage{Names:[mcr.microsoft.com/oss/kubernetes-csi/livenessprobe@sha256:fcb73e1939d9abeb2d1e1680b476a10a422a04a73ea5a65e64eec3fde1f2a5a1 mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.8.0],SizeBytes:9117963,},ContainerImage{Names:[docker.io/calico/csi@sha256:61a95f3ee79a7e591aff9eff535be73e62d2c3931d07c2ea8a1305f7bea19b31 docker.io/calico/csi:v3.25.0],SizeBytes:9076936,},ContainerImage{Names:[docker.io/calico/pod2daemon-flexvol@sha256:01ddd57d428787b3ac689daa685660defe4bd7810069544bd43a9103a7b0a789 docker.io/calico/pod2daemon-flexvol:v3.25.0],SizeBytes:7076045,},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 16 17:23:58.172: INFO: 
  Logging kubelet events for node capz-conf-vmxw18-md-0-chndb
  Jan 16 17:23:58.371: INFO: 
  Logging pods the kubelet thinks is on node capz-conf-vmxw18-md-0-chndb
  Jan 16 17:23:58.589: INFO: calico-node-xj2jq started at 2023-01-16 17:13:00 +0000 UTC (2+1 container statuses recorded)
  Jan 16 17:23:58.589: INFO: 	Init container flexvol-driver ready: true, restart count 0
  Jan 16 17:23:58.589: INFO: 	Init container install-cni ready: true, restart count 0
  Jan 16 17:23:58.589: INFO: 	Container calico-node ready: true, restart count 0
  Jan 16 17:23:58.589: INFO: csi-azuredisk-node-w4jmz started at 2023-01-16 17:13:00 +0000 UTC (0+3 container statuses recorded)
  Jan 16 17:23:58.589: INFO: 	Container azuredisk ready: true, restart count 0
  Jan 16 17:23:58.589: INFO: 	Container liveness-probe ready: true, restart count 0
  Jan 16 17:23:58.589: INFO: 	Container node-driver-registrar ready: true, restart count 0
  Jan 16 17:23:58.589: INFO: kube-proxy-gk5hh started at 2023-01-16 17:13:00 +0000 UTC (0+1 container statuses recorded)
  Jan 16 17:23:58.589: INFO: 	Container kube-proxy ready: true, restart count 0
  Jan 16 17:23:58.589: INFO: csi-node-driver-j6m4h started at 2023-01-16 17:13:22 +0000 UTC (0+2 container statuses recorded)
  Jan 16 17:23:58.589: INFO: 	Container calico-csi ready: true, restart count 0
  Jan 16 17:23:58.589: INFO: 	Container csi-node-driver-registrar ready: true, restart count 0
  Jan 16 17:23:59.211: INFO: 
  Latency metrics for node capz-conf-vmxw18-md-0-chndb
  Jan 16 17:23:59.397: INFO: Running kubectl logs on non-ready containers in kube-system
  Jan 16 17:23:59.787: INFO: Failed to get logs of pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf)
  Jan 16 17:23:59.787: INFO: Logs of kube-system/kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf:kube-apiserver on node capz-conf-vmxw18-control-plane-kxjwf
  Jan 16 17:23:59.787: INFO:  : STARTLOG

  ENDLOG for container kube-system:kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf:kube-apiserver
  Jan 16 17:24:00.172: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf)
  Jan 16 17:24:00.172: INFO: Logs of kube-system/kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf:kube-controller-manager on node capz-conf-vmxw18-control-plane-kxjwf
  Jan 16 17:24:00.172: INFO:  : STARTLOG

  ENDLOG for container kube-system:kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf:kube-controller-manager
  Jan 16 17:24:00.571: INFO: Failed to get logs of pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf)
  Jan 16 17:24:00.571: INFO: Logs of kube-system/kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf:kube-scheduler on node capz-conf-vmxw18-control-plane-kxjwf
  Jan 16 17:24:00.571: INFO:  : STARTLOG

  ENDLOG for container kube-system:kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf:kube-scheduler
  �[38;5;9m[FAILED]�[0m in [SynchronizedBeforeSuite] - test/e2e/e2e.go:251 �[38;5;243m@ 01/16/23 17:24:00.572�[0m
  �[38;5;243m<< Timeline�[0m

  �[38;5;9m[FAILED] 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-vmxw18-control-plane-kxjwf          capz-conf-vmxw18-control-plane-kxjwf Pending       []
  kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf capz-conf-vmxw18-control-plane-kxjwf Pending       []
  kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf          capz-conf-vmxw18-control-plane-kxjwf Running       [{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-16 17:10:16 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-16 17:10:16 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [kube-scheduler]} {Type:ContainersReady Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-16 17:10:16 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [kube-scheduler]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2023-01-16 17:10:16 +0000 UTC Reason: Message:}]
  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:251�[0m �[38;5;243m@ 01/16/23 17:24:00.572�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [636.761 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.662�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [636.818 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.663�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [636.831 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.669�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [636.856 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.671�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [637.127 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.664�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [637.133 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.671�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [637.132 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.671�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [637.070 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.671�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [637.137 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.672�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [636.883 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.672�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [637.360 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.663�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [636.996 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.663�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [636.929 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.677�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [636.785 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.676�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [637.036 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.677�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [636.925 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.672�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [636.859 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.678�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [636.789 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.675�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [637.010 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.671�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [637.225 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.678�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [636.896 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.677�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [637.091 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m

  �[38;5;9m[FAILED] �[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
    The first SynchronizedBeforeSuite function running on Ginkgo parallel process
    #1 failed.  This suite will now abort.

  �[0m
  �[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m �[38;5;243m@ 01/16/23 17:24:00.67�[0m
�[38;5;243m------------------------------�[0m

�[38;5;9m�[1mSummarizing 25 Failures:�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:77�[0m
  �[38;5;9m[FAIL]�[0m �[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
  �[38;5;243mtest/e2e/e2e.go:251�[0m

�[38;5;9m�[1mRan 0 of 7072 Specs in 637.987 seconds�[0m
�[38;5;9m�[1mFAIL!�[0m -- �[38;5;14m�[1mA BeforeSuite node failed so all tests were skipped.�[0m

  I0116 17:13:21.561490      13 e2e.go:126] Starting e2e run "c2ca044c-6aee-434a-8f53-b1e79c3b8c30" on Ginkgo node 1
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (639.33s)
FAIL

  I0116 17:13:21.582246      15 e2e.go:126] Starting e2e run "94b47dad-830c-4ed6-b746-b657751f35a1" on Ginkgo node 2
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (639.15s)
FAIL

  I0116 17:13:21.549817      16 e2e.go:126] Starting e2e run "931c93e0-9fe9-4b13-b60e-8d9dcf38fec2" on Ginkgo node 3
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (639.17s)
FAIL

  I0116 17:13:21.585726      17 e2e.go:126] Starting e2e run "3e5a8a3a-2d99-45fe-bf91-840e0e1ee260" on Ginkgo node 4
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (639.13s)
FAIL

  I0116 17:13:21.456282      19 e2e.go:126] Starting e2e run "dc64291f-21d4-42e5-b4c2-9bec6da9574e" on Ginkgo node 5
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (639.23s)
FAIL

  I0116 17:13:21.816577      22 e2e.go:126] Starting e2e run "d78db438-3d45-4577-89ab-c987d3dfc07e" on Ginkgo node 6
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.92s)
FAIL

  I0116 17:13:21.917223      41 e2e.go:126] Starting e2e run "034bc33c-0928-4834-a602-b1468183ca94" on Ginkgo node 7
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.81s)
FAIL

  I0116 17:13:22.013379      58 e2e.go:126] Starting e2e run "73316257-fb5e-43ae-9fd4-94713579aaf4" on Ginkgo node 8
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.66s)
FAIL

  I0116 17:13:21.929904      62 e2e.go:126] Starting e2e run "0abf44c9-9ad5-416d-b3f0-0591b8ad8692" on Ginkgo node 9
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.79s)
FAIL

  I0116 17:13:21.869230      68 e2e.go:126] Starting e2e run "69e56a7e-c7c9-40c4-9ca0-7361239afe91" on Ginkgo node 10
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.89s)
FAIL

  I0116 17:13:22.145812      72 e2e.go:126] Starting e2e run "e4cbdcf0-1d7c-4850-b17d-5ffa80eadb30" on Ginkgo node 11
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.52s)
FAIL

  I0116 17:13:22.188659      83 e2e.go:126] Starting e2e run "aba15ebd-e3cc-422d-9c83-1f5da6527c9c" on Ginkgo node 12
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.53s)
FAIL

  I0116 17:13:22.046558      93 e2e.go:126] Starting e2e run "bf36a8f4-436d-469e-b381-27f84dd4cb2c" on Ginkgo node 13
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.65s)
FAIL

  I0116 17:13:21.836991      95 e2e.go:126] Starting e2e run "f6598d41-6db8-4a6e-8a9c-9290179f852a" on Ginkgo node 14
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.88s)
FAIL

  I0116 17:13:22.124948      96 e2e.go:126] Starting e2e run "b35bbd45-033b-4840-9ec4-fe3972811b1e" on Ginkgo node 15
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.59s)
FAIL

  I0116 17:13:22.158779     110 e2e.go:126] Starting e2e run "569912b5-bd39-408e-a8b8-0984a8684b1a" on Ginkgo node 16
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.57s)
FAIL

  I0116 17:13:21.834437     122 e2e.go:126] Starting e2e run "fd2f1a0a-12a5-4a58-b16e-0a273b6660cf" on Ginkgo node 17
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.88s)
FAIL

  I0116 17:13:21.935465     127 e2e.go:126] Starting e2e run "a127bfeb-0a24-4f86-a83c-be36a39283a0" on Ginkgo node 18
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.78s)
FAIL

  I0116 17:13:22.105104     135 e2e.go:126] Starting e2e run "24f7abc4-1202-470d-8206-d34791750795" on Ginkgo node 19
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.61s)
FAIL

  I0116 17:13:21.963196     140 e2e.go:126] Starting e2e run "c1cf093c-6631-4331-9aeb-f1d21692abc8" on Ginkgo node 20
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.79s)
FAIL

  I0116 17:13:22.391422     183 e2e.go:126] Starting e2e run "2e03400c-f8a8-4fd8-8a16-ab48bc226266" on Ginkgo node 21
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.33s)
FAIL

  I0116 17:13:22.025380     189 e2e.go:126] Starting e2e run "5d2dc8fd-afbf-4942-ba39-cbf4648d285c" on Ginkgo node 22
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.72s)
FAIL

  I0116 17:13:22.354723     194 e2e.go:126] Starting e2e run "9c0bd3c8-2a76-4eac-8317-98c0e3d9f579" on Ginkgo node 23
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.35s)
FAIL

  I0116 17:13:22.302004     199 e2e.go:126] Starting e2e run "b4b6051e-1272-4ae2-b04e-888ae56edc1f" on Ginkgo node 24
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.41s)
FAIL

  I0116 17:13:22.557880     211 e2e.go:126] Starting e2e run "a5331229-1620-4d54-a248-1dadf2bcb44c" on Ginkgo node 25
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--ginkgo.slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo.  This feature has proved to be more noisy than useful.  You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck.�[0m
  �[38;5;11m--ginkgo.progress is deprecated .  The functionality provided by --progress was confusing and is no longer needed.  Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs.  Or you can run with -vv to always see all node events.  Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck.�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

--- FAIL: TestE2E (638.14s)
FAIL


Ginkgo ran 1 suite in 10m39.965283057s

Test Suite Failed
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
  �[38;5;11m--slowSpecThreshold is deprecated use --slow-spec-threshold instead and pass in a duration string (e.g. '5s', not '5.0')�[0m
  �[1mLearn more at:�[0m �[38;5;14m�[4mhttps://onsi.github.io/ginkgo/MIGRATING_TO_V2#changed--slowspecthreshold�[0m

�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
  �[38;5;243mACK_GINKGO_DEPRECATIONS=2.7.0�[0m

[FAILED] Unexpected error:
    <*errors.withStack | 0xc0023ad668>: {
        error: <*errors.withMessage | 0xc0010b44c0>{
            cause: <*errors.errorString | 0xc00102a930>{
                s: "error container run failed with exit code 1",
            },
            msg: "Unable to run conformance tests",
        },
        stack: [0x3143419, 0x353bb67, 0x18e639b, 0x18f9e98, 0x147c741],
    }
    Unable to run conformance tests: error container run failed with exit code 1
occurred
In [It] at: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:238 @ 01/16/23 17:24:01.502
< Exit [It] conformance-tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100 @ 01/16/23 17:24:01.502 (17m21.158s)
> Enter [AfterEach] Conformance Tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:242 @ 01/16/23 17:24:01.502
Jan 16 17:24:01.504: INFO: FAILED!
Jan 16 17:24:01.506: INFO: Cleaning up after "Conformance Tests conformance-tests" spec
STEP: Dumping logs from the "capz-conf-vmxw18" workload cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:88 @ 01/16/23 17:24:01.506
Jan 16 17:24:01.506: INFO: Dumping workload cluster capz-conf-vmxw18/capz-conf-vmxw18 logs
Jan 16 17:24:01.606: INFO: Collecting logs for Linux node capz-conf-vmxw18-control-plane-kxjwf in cluster capz-conf-vmxw18 in namespace capz-conf-vmxw18

Jan 16 17:24:14.090: INFO: Collecting boot logs for AzureMachine capz-conf-vmxw18-control-plane-kxjwf

Jan 16 17:24:15.155: INFO: Collecting logs for Linux node capz-conf-vmxw18-md-0-chndb in cluster capz-conf-vmxw18 in namespace capz-conf-vmxw18

Jan 16 17:24:24.623: INFO: Collecting boot logs for AzureMachine capz-conf-vmxw18-md-0-chndb

Jan 16 17:24:25.105: INFO: Collecting logs for Linux node capz-conf-vmxw18-md-0-2zlxc in cluster capz-conf-vmxw18 in namespace capz-conf-vmxw18

Jan 16 17:24:34.551: INFO: Collecting boot logs for AzureMachine capz-conf-vmxw18-md-0-2zlxc

Jan 16 17:24:35.084: INFO: Dumping workload cluster capz-conf-vmxw18/capz-conf-vmxw18 kube-system pod logs
Jan 16 17:24:35.439: INFO: Collecting events for Pod calico-apiserver/calico-apiserver-86685f5cdf-gh5z5
Jan 16 17:24:35.439: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-86685f5cdf-gh5z5, container calico-apiserver
Jan 16 17:24:35.439: INFO: Creating log watcher for controller calico-apiserver/calico-apiserver-86685f5cdf-kxmzb, container calico-apiserver
Jan 16 17:24:35.439: INFO: Collecting events for Pod calico-apiserver/calico-apiserver-86685f5cdf-kxmzb
Jan 16 17:24:35.509: INFO: Creating log watcher for controller calico-system/calico-kube-controllers-6b7b9c649d-d649m, container calico-kube-controllers
Jan 16 17:24:35.509: INFO: Collecting events for Pod calico-system/calico-node-vlwbv
Jan 16 17:24:35.509: INFO: Creating log watcher for controller calico-system/calico-node-6sbp2, container calico-node
Jan 16 17:24:35.510: INFO: Collecting events for Pod calico-system/calico-node-6sbp2
Jan 16 17:24:35.510: INFO: Creating log watcher for controller calico-system/calico-node-vlwbv, container calico-node
Jan 16 17:24:35.510: INFO: Collecting events for Pod calico-system/calico-kube-controllers-6b7b9c649d-d649m
Jan 16 17:24:35.510: INFO: Creating log watcher for controller calico-system/csi-node-driver-6zqjc, container calico-csi
Jan 16 17:24:35.510: INFO: Creating log watcher for controller calico-system/calico-typha-5dbf8c789f-tjklr, container calico-typha
Jan 16 17:24:35.510: INFO: Creating log watcher for controller calico-system/calico-node-xj2jq, container calico-node
Jan 16 17:24:35.510: INFO: Creating log watcher for controller calico-system/calico-typha-5dbf8c789f-tnftc, container calico-typha
Jan 16 17:24:35.511: INFO: Creating log watcher for controller calico-system/csi-node-driver-6zqjc, container csi-node-driver-registrar
Jan 16 17:24:35.511: INFO: Collecting events for Pod calico-system/calico-node-xj2jq
Jan 16 17:24:35.511: INFO: Collecting events for Pod calico-system/calico-typha-5dbf8c789f-tnftc
Jan 16 17:24:35.511: INFO: Collecting events for Pod calico-system/calico-typha-5dbf8c789f-tjklr
Jan 16 17:24:35.511: INFO: Collecting events for Pod calico-system/csi-node-driver-j6m4h
Jan 16 17:24:35.511: INFO: Collecting events for Pod calico-system/csi-node-driver-6zqjc
Jan 16 17:24:35.511: INFO: Creating log watcher for controller calico-system/csi-node-driver-j6m4h, container calico-csi
Jan 16 17:24:35.511: INFO: Creating log watcher for controller calico-system/csi-node-driver-j6m4h, container csi-node-driver-registrar
Jan 16 17:24:35.511: INFO: Creating log watcher for controller calico-system/csi-node-driver-kcrm6, container csi-node-driver-registrar
Jan 16 17:24:35.511: INFO: Creating log watcher for controller calico-system/csi-node-driver-kcrm6, container calico-csi
Jan 16 17:24:35.511: INFO: Collecting events for Pod calico-system/csi-node-driver-kcrm6
Jan 16 17:24:35.564: INFO: Collecting events for Pod kube-system/coredns-56f4c55bf9-kflz4
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/etcd-capz-conf-vmxw18-control-plane-kxjwf, container etcd
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/csi-azuredisk-node-w4jmz, container liveness-probe
Jan 16 17:24:35.564: INFO: Collecting events for Pod kube-system/etcd-capz-conf-vmxw18-control-plane-kxjwf
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf, container kube-controller-manager
Jan 16 17:24:35.564: INFO: Collecting events for Pod kube-system/kube-proxy-gk5hh
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/coredns-56f4c55bf9-sgp4s, container coredns
Jan 16 17:24:35.564: INFO: Collecting events for Pod kube-system/coredns-56f4c55bf9-sgp4s
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/csi-azuredisk-node-pkv8r, container liveness-probe
Jan 16 17:24:35.565: INFO: Creating log watcher for controller kube-system/kube-proxy-snp29, container kube-proxy
Jan 16 17:24:35.565: INFO: Collecting events for Pod kube-system/kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf
Jan 16 17:24:35.565: INFO: Creating log watcher for controller kube-system/kube-proxy-g6257, container kube-proxy
Jan 16 17:24:35.566: INFO: Creating log watcher for controller kube-system/kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf, container kube-apiserver
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/csi-azuredisk-controller-7c87ff77db-6868l, container liveness-probe
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/csi-azuredisk-controller-7c87ff77db-6868l, container azuredisk
Jan 16 17:24:35.566: INFO: Creating log watcher for controller kube-system/kube-proxy-gk5hh, container kube-proxy
Jan 16 17:24:35.566: INFO: Collecting events for Pod kube-system/kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf
Jan 16 17:24:35.564: INFO: Collecting events for Pod kube-system/csi-azuredisk-node-pkv8r
Jan 16 17:24:35.566: INFO: Creating log watcher for controller kube-system/metrics-server-c9574f845-2hxlf, container metrics-server
Jan 16 17:24:35.566: INFO: Collecting events for Pod kube-system/metrics-server-c9574f845-2hxlf
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/csi-azuredisk-controller-7c87ff77db-6868l, container csi-attacher
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/csi-azuredisk-controller-7c87ff77db-6868l, container csi-snapshotter
Jan 16 17:24:35.566: INFO: Creating log watcher for controller kube-system/kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf, container kube-scheduler
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/csi-azuredisk-node-kw4f7, container azuredisk
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/csi-azuredisk-controller-7c87ff77db-6868l, container csi-resizer
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/coredns-56f4c55bf9-kflz4, container coredns
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/csi-azuredisk-node-kw4f7, container liveness-probe
Jan 16 17:24:35.564: INFO: Collecting events for Pod kube-system/csi-azuredisk-node-kw4f7
Jan 16 17:24:35.564: INFO: Collecting events for Pod kube-system/kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/csi-azuredisk-node-w4jmz, container node-driver-registrar
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/csi-azuredisk-node-w4jmz, container azuredisk
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/csi-azuredisk-node-pkv8r, container node-driver-registrar
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/csi-azuredisk-node-pkv8r, container azuredisk
Jan 16 17:24:35.564: INFO: Collecting events for Pod kube-system/csi-azuredisk-node-w4jmz
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/csi-azuredisk-controller-7c87ff77db-6868l, container csi-provisioner
Jan 16 17:24:35.566: INFO: Collecting events for Pod kube-system/kube-proxy-g6257
Jan 16 17:24:35.566: INFO: Collecting events for Pod kube-system/kube-proxy-snp29
Jan 16 17:24:35.564: INFO: Collecting events for Pod kube-system/csi-azuredisk-controller-7c87ff77db-6868l
Jan 16 17:24:35.564: INFO: Creating log watcher for controller kube-system/csi-azuredisk-node-kw4f7, container node-driver-registrar
Jan 16 17:24:35.616: INFO: Fetching kube-system pod logs took 531.05972ms
Jan 16 17:24:35.616: INFO: Dumping workload cluster capz-conf-vmxw18/capz-conf-vmxw18 Azure activity log
Jan 16 17:24:35.616: INFO: Creating log watcher for controller tigera-operator/tigera-operator-54b47459dd-pg6mz, container tigera-operator
Jan 16 17:24:35.616: INFO: Collecting events for Pod tigera-operator/tigera-operator-54b47459dd-pg6mz
Jan 16 17:24:35.629: INFO: Error starting logs stream for pod kube-system/kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf, container kube-controller-manager: container "kube-controller-manager" in pod "kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf" is not available
Jan 16 17:24:35.669: INFO: Error starting logs stream for pod kube-system/kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf, container kube-scheduler: container "kube-scheduler" in pod "kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf" is not available
Jan 16 17:24:35.686: INFO: Error starting logs stream for pod kube-system/kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf, container kube-apiserver: container "kube-apiserver" in pod "kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf" is not available
Jan 16 17:24:39.544: INFO: Fetching activity logs took 3.928266147s
Jan 16 17:24:39.544: INFO: Dumping all the Cluster API resources in the "capz-conf-vmxw18" namespace
Jan 16 17:24:40.029: INFO: Deleting all clusters in the capz-conf-vmxw18 namespace
STEP: Deleting cluster capz-conf-vmxw18 - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/ginkgoextensions/output.go:35 @ 01/16/23 17:24:40.051
INFO: Waiting for the Cluster capz-conf-vmxw18/capz-conf-vmxw18 to be deleted
STEP: Waiting for cluster capz-conf-vmxw18 to be deleted - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.1/framework/ginkgoextensions/output.go:35 @ 01/16/23 17:24:40.072
Jan 16 17:30:20.278: INFO: Deleting namespace used for hosting the "conformance-tests" test spec
INFO: Deleting namespace capz-conf-vmxw18
Jan 16 17:30:20.297: INFO: Checking if any resources are left over in Azure for spec "conformance-tests"
STEP: Redacting sensitive information from logs - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:212 @ 01/16/23 17:30:20.901
< Exit [AfterEach] Conformance Tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:242 @ 01/16/23 17:30:39.337 (6m37.834s)

				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid

Error lines from build-log.txt

Raw build-log.txt

... skipping 121 lines ...
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   138  100   138    0     0   3209      0 --:--:-- --:--:-- --:--:--  3209

100    34  100    34    0     0    361      0 --:--:-- --:--:-- --:--:--   361
using CI_VERSION=v1.27.0-alpha.0.999+ed8cad1e80d096
using KUBERNETES_VERSION=v1.27.0-alpha.0.999+ed8cad1e80d096
using IMAGE_TAG=v1.27.0-alpha.0.1003_d9497132775a68
Error response from daemon: manifest for capzci.azurecr.io/kube-apiserver:v1.27.0-alpha.0.1003_d9497132775a68 not found: manifest unknown: manifest tagged by "v1.27.0-alpha.0.1003_d9497132775a68" is not found
Building Kubernetes
make: Entering directory '/home/prow/go/src/k8s.io/kubernetes'
+++ [0116 16:36:07] Verifying Prerequisites....
+++ [0116 16:36:08] Building Docker image kube-build:build-37a7b80327-5-v1.26.0-go1.19.5-bullseye.0
+++ [0116 16:39:44] Creating data container kube-build-data-37a7b80327-5-v1.26.0-go1.19.5-bullseye.0
+++ [0116 16:40:08] Syncing sources to container
... skipping 661 lines ...
[38;5;243m------------------------------[0m
[0mConformance Tests [0m[1mconformance-tests[0m
[38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100[0m
  INFO: Cluster name is capz-conf-vmxw18
  [1mSTEP:[0m Creating namespace "capz-conf-vmxw18" for hosting the cluster [38;5;243m@ 01/16/23 17:06:40.263[0m
  Jan 16 17:06:40.263: INFO: starting to create namespace for hosting the "capz-conf-vmxw18" test spec
2023/01/16 17:06:40 failed trying to get namespace (capz-conf-vmxw18):namespaces "capz-conf-vmxw18" not found
  INFO: Creating namespace capz-conf-vmxw18
  INFO: Creating event watcher for namespace "capz-conf-vmxw18"
  [1mconformance-tests[38;5;243m - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:102 @ 01/16/23 17:06:40.344[0m
    [1mconformance-tests
    [0m[1mName[0m | [1mN[0m | [1mMin[0m | [1mMedian[0m | [1mMean[0m | [1mStdDev[0m | [1mMax[0m
  INFO: Creating the workload cluster with name "capz-conf-vmxw18" using the "conformance-presubmit-artifacts" template (Kubernetes v1.27.0-alpha.0.999+ed8cad1e80d096, 1 control-plane machines, 2 worker machines)
... skipping 117 lines ...
  ====================================================
  Random Seed: [1m1673889200[0m - will randomize all specs
  
  Will run [1m344[0m of [1m7072[0m specs
  Running in parallel across [1m25[0m processes
  [38;5;243m------------------------------[0m
  [38;5;9m[SynchronizedBeforeSuite] [FAILED] [636.833 seconds][0m

  [38;5;9m[1m[SynchronizedBeforeSuite] [0m
  [38;5;243mtest/e2e/e2e.go:77[0m
  
    [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m

      The first SynchronizedBeforeSuite function running on Ginkgo parallel process
      #1 failed.  This suite will now abort.

  
    [0m
    [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/16/23 17:24:00.58[0m
  [38;5;243m------------------------------[0m
  [38;5;9m[SynchronizedBeforeSuite] [FAILED] [637.040 seconds][0m

  [38;5;9m[1m[SynchronizedBeforeSuite] [0m
  [38;5;243mtest/e2e/e2e.go:77[0m
  
    [38;5;9m[FAILED] [1m[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1[0m

      The first SynchronizedBeforeSuite function running on Ginkgo parallel process
      #1 failed.  This suite will now abort.

  
    [0m
    [38;5;9mIn [1m[SynchronizedBeforeSuite][0m[38;5;9m at: [1mtest/e2e/e2e.go:77[0m [38;5;243m@ 01/16/23 17:24:00.581[0m
  [38;5;243m------------------------------[0m
  [38;5;9m[SynchronizedBeforeSuite] [FAILED] [637.693 seconds][0m

  [38;5;9m[1m[SynchronizedBeforeSuite] [0m
  [38;5;243mtest/e2e/e2e.go:77[0m
  
    [38;5;243mTimeline >>[0m
    Jan 16 17:13:22.880: INFO: >>> kubeConfig: /tmp/kubeconfig
    Jan 16 17:13:22.883: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
    Jan 16 17:13:23.103: INFO: Condition Ready of node capz-conf-vmxw18-md-0-2zlxc is false, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready  NoSchedule <nil>} {node.kubernetes.io/not-ready  NoExecute 2023-01-16 17:13:04 +0000 UTC}]. Failure
    Jan 16 17:13:23.103: INFO: Condition Ready of node capz-conf-vmxw18-md-0-chndb is true, but Node is tainted by NodeController with [{node.kubernetes.io/not-ready  NoExecute 2023-01-16 17:12:54 +0000 UTC}]. Failure
    Jan 16 17:13:23.103: INFO: Unschedulable nodes= 2, maximum value for starting tests= 0
    Jan 16 17:13:23.103: INFO: 	-> Node capz-conf-vmxw18-md-0-2zlxc [[[ Ready=false, Network(available)=false, Taints=[{node.kubernetes.io/not-ready  NoSchedule <nil>} {node.kubernetes.io/not-ready  NoExecute 2023-01-16 17:13:04 +0000 UTC}], NonblockingTaints=node-role.kubernetes.io/control-plane,node-role.kubernetes.io/master ]]]
    Jan 16 17:13:23.103: INFO: 	-> Node capz-conf-vmxw18-md-0-chndb [[[ Ready=false, Network(available)=false, Taints=[{node.kubernetes.io/not-ready  NoExecute 2023-01-16 17:12:54 +0000 UTC}], NonblockingTaints=node-role.kubernetes.io/control-plane,node-role.kubernetes.io/master ]]]
    Jan 16 17:13:23.103: INFO: ==== node wait: 1 out of 3 nodes are ready, max notReady allowed 0.  Need 2 more before starting.
    Jan 16 17:13:53.150: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
    Jan 16 17:13:53.336: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:13:53.336: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:13:53.336: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:13:53.336: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
    Jan 16 17:13:53.336: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:13:53.336: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:13:53.336: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:13:53.336: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:13:53.336: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:13:53.336: INFO: 
    Jan 16 17:13:55.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:13:55.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:13:55.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:13:55.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
    Jan 16 17:13:55.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:13:55.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:13:55.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:13:55.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:13:55.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:13:55.459: INFO: 
    Jan 16 17:13:57.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:13:57.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:13:57.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:13:57.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
    Jan 16 17:13:57.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:13:57.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:13:57.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:13:57.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:13:57.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:13:57.455: INFO: 
    Jan 16 17:13:59.468: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:13:59.468: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:13:59.468: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:13:59.468: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
    Jan 16 17:13:59.468: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:13:59.468: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:13:59.468: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:13:59.468: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:13:59.468: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:13:59.468: INFO: 
    Jan 16 17:14:01.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:01.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:01.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:01.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
    Jan 16 17:14:01.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:01.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:01.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:01.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:01.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:01.459: INFO: 
    Jan 16 17:14:03.461: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:03.461: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:03.461: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:03.461: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
    Jan 16 17:14:03.461: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:03.461: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:03.461: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:03.461: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:03.461: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:03.461: INFO: 
    Jan 16 17:14:05.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:05.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:05.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:05.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
    Jan 16 17:14:05.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:05.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:05.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:05.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:05.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:05.454: INFO: 
    Jan 16 17:14:07.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:07.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:07.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:07.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
    Jan 16 17:14:07.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:07.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:07.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:07.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:07.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:07.457: INFO: 
    Jan 16 17:14:09.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:09.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:09.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:09.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
    Jan 16 17:14:09.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:09.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:09.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:09.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:09.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:09.454: INFO: 
    Jan 16 17:14:11.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:11.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:11.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:11.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
    Jan 16 17:14:11.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:11.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:11.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:11.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:11.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:11.454: INFO: 
    Jan 16 17:14:13.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:13.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:13.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:13.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
    Jan 16 17:14:13.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:13.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:13.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:13.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:13.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:13.454: INFO: 
    Jan 16 17:14:15.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:15.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:15.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:15.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
    Jan 16 17:14:15.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:15.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:15.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:15.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:15.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:15.452: INFO: 
    Jan 16 17:14:17.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:17.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:17.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:17.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
    Jan 16 17:14:17.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:17.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:17.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:17.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:17.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:17.453: INFO: 
    Jan 16 17:14:19.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:19.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:19.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:19.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
    Jan 16 17:14:19.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:19.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:19.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:19.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:19.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:19.454: INFO: 
    Jan 16 17:14:21.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:21.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:21.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:21.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
    Jan 16 17:14:21.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:21.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:21.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:21.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:21.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:21.457: INFO: 
    Jan 16 17:14:23.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:23.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:23.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:23.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
    Jan 16 17:14:23.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:23.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:23.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:23.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:23.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:23.459: INFO: 
    Jan 16 17:14:25.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:25.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:25.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:25.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
    Jan 16 17:14:25.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:25.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:25.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:25.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:25.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:25.454: INFO: 
    Jan 16 17:14:27.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:27.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:27.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:27.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
    Jan 16 17:14:27.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:27.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:27.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:27.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:27.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:27.455: INFO: 
    Jan 16 17:14:29.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:29.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:29.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:29.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
    Jan 16 17:14:29.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:29.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:29.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:29.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:29.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:29.453: INFO: 
    Jan 16 17:14:31.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:31.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:31.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:31.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
    Jan 16 17:14:31.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:31.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:31.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:31.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:31.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:31.454: INFO: 
    Jan 16 17:14:33.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:33.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:33.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:33.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
    Jan 16 17:14:33.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:33.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:33.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:33.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:33.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:33.454: INFO: 
    Jan 16 17:14:35.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:35.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:35.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:35.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
    Jan 16 17:14:35.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:35.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:35.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:35.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:35.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:35.452: INFO: 
    Jan 16 17:14:37.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:37.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:37.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:37.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
    Jan 16 17:14:37.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:37.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:37.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:37.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:37.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:37.453: INFO: 
    Jan 16 17:14:39.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:39.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:39.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:39.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
    Jan 16 17:14:39.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:39.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:39.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:39.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:39.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:39.454: INFO: 
    Jan 16 17:14:41.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:41.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:41.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:41.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
    Jan 16 17:14:41.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:41.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:41.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:41.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:41.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:41.455: INFO: 
    Jan 16 17:14:43.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:43.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:43.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:43.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
    Jan 16 17:14:43.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:43.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:43.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:43.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:43.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:43.456: INFO: 
    Jan 16 17:14:45.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:45.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:45.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:45.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
    Jan 16 17:14:45.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:45.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:45.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:45.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:45.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:45.458: INFO: 
    Jan 16 17:14:47.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:47.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:47.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:47.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
    Jan 16 17:14:47.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:47.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:47.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:47.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:47.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:47.454: INFO: 
    Jan 16 17:14:49.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:49.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:49.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:49.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
    Jan 16 17:14:49.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:49.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:49.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:49.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:49.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:49.454: INFO: 
    Jan 16 17:14:51.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:51.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:51.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:51.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
    Jan 16 17:14:51.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:51.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:51.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:51.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:51.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:51.456: INFO: 
    Jan 16 17:14:53.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:53.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:53.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:53.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
    Jan 16 17:14:53.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:53.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:53.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:53.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:53.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:53.454: INFO: 
    Jan 16 17:14:55.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:55.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:55.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:55.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
    Jan 16 17:14:55.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:55.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:55.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:55.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:55.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:55.456: INFO: 
    Jan 16 17:14:57.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:57.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:57.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:57.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
    Jan 16 17:14:57.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:57.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:57.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:57.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:57.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:57.453: INFO: 
    Jan 16 17:14:59.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:59.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:59.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:14:59.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
    Jan 16 17:14:59.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:14:59.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:14:59.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:59.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:14:59.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:14:59.455: INFO: 
    Jan 16 17:15:01.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:01.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:01.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:01.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
    Jan 16 17:15:01.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:01.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:01.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:01.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:01.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:01.456: INFO: 
    Jan 16 17:15:03.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:03.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:03.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:03.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
    Jan 16 17:15:03.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:03.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:03.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:03.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:03.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:03.454: INFO: 
    Jan 16 17:15:05.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:05.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:05.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:05.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
    Jan 16 17:15:05.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:05.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:05.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:05.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:05.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:05.456: INFO: 
    Jan 16 17:15:07.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:07.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:07.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:07.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
    Jan 16 17:15:07.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:07.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:07.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:07.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:07.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:07.455: INFO: 
    Jan 16 17:15:09.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:09.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:09.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:09.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
    Jan 16 17:15:09.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:09.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:09.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:09.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:09.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:09.454: INFO: 
    Jan 16 17:15:11.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:11.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:11.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:11.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
    Jan 16 17:15:11.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:11.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:11.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:11.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:11.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:11.452: INFO: 
    Jan 16 17:15:13.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:13.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:13.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:13.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
    Jan 16 17:15:13.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:13.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:13.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:13.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:13.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:13.455: INFO: 
    Jan 16 17:15:15.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:15.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:15.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:15.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
    Jan 16 17:15:15.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:15.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:15.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:15.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:15.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:15.453: INFO: 
    Jan 16 17:15:17.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:17.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:17.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:17.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
    Jan 16 17:15:17.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:17.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:17.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:17.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:17.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:17.455: INFO: 
    Jan 16 17:15:19.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:19.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:19.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:19.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
    Jan 16 17:15:19.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:19.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:19.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:19.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:19.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:19.454: INFO: 
    Jan 16 17:15:21.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:21.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:21.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:21.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
    Jan 16 17:15:21.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:21.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:21.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:21.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:21.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:21.454: INFO: 
    Jan 16 17:15:23.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:23.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:23.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:23.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
    Jan 16 17:15:23.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:23.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:23.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:23.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:23.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:23.453: INFO: 
    Jan 16 17:15:25.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:25.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:25.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:25.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
    Jan 16 17:15:25.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:25.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:25.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:25.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:25.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:25.453: INFO: 
    Jan 16 17:15:27.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:27.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:27.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:27.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
    Jan 16 17:15:27.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:27.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:27.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:27.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:27.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:27.454: INFO: 
    Jan 16 17:15:29.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:29.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:29.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:29.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
    Jan 16 17:15:29.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:29.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:29.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:29.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:29.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:29.455: INFO: 
    Jan 16 17:15:31.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:31.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:31.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:31.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
    Jan 16 17:15:31.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:31.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:31.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:31.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:31.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:31.454: INFO: 
    Jan 16 17:15:33.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:33.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:33.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:33.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
    Jan 16 17:15:33.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:33.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:33.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:33.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:33.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:33.455: INFO: 
    Jan 16 17:15:35.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:35.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:35.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:35.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
    Jan 16 17:15:35.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:35.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:35.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:35.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:35.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:35.452: INFO: 
    Jan 16 17:15:37.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:37.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:37.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:37.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
    Jan 16 17:15:37.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:37.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:37.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:37.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:37.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:37.453: INFO: 
    Jan 16 17:15:39.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:39.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:39.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:39.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
    Jan 16 17:15:39.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:39.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:39.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:39.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:39.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:39.456: INFO: 
    Jan 16 17:15:41.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:41.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:41.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:41.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
    Jan 16 17:15:41.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:41.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:41.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:41.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:41.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:41.453: INFO: 
    Jan 16 17:15:43.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:43.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:43.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:43.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
    Jan 16 17:15:43.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:43.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:43.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:43.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:43.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:43.452: INFO: 
    Jan 16 17:15:45.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:45.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:45.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:45.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
    Jan 16 17:15:45.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:45.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:45.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:45.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:45.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:45.453: INFO: 
    Jan 16 17:15:47.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:47.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:47.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:47.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
    Jan 16 17:15:47.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:47.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:47.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:47.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:47.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:47.456: INFO: 
    Jan 16 17:15:49.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:49.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:49.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:49.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
    Jan 16 17:15:49.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:49.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:49.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:49.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:49.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:49.457: INFO: 
    Jan 16 17:15:51.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:51.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:51.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:51.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
    Jan 16 17:15:51.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:51.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:51.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:51.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:51.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:51.453: INFO: 
    Jan 16 17:15:53.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:53.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:53.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:53.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
    Jan 16 17:15:53.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:53.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:53.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:53.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:53.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:53.457: INFO: 
    Jan 16 17:15:55.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:55.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:55.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:55.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
    Jan 16 17:15:55.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:55.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:55.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:55.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:55.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:55.454: INFO: 
    Jan 16 17:15:57.458: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:57.458: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:57.458: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:57.458: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
    Jan 16 17:15:57.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:57.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:57.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:57.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:57.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:57.458: INFO: 
    Jan 16 17:15:59.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:59.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:59.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:15:59.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
    Jan 16 17:15:59.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:15:59.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:15:59.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:59.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:15:59.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:15:59.457: INFO: 
    Jan 16 17:16:01.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:01.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:01.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:01.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
    Jan 16 17:16:01.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:01.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:01.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:01.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:01.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:01.455: INFO: 
    Jan 16 17:16:03.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:03.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:03.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:03.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
    Jan 16 17:16:03.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:03.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:03.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:03.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:03.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:03.454: INFO: 
    Jan 16 17:16:05.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:05.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:05.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:05.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
    Jan 16 17:16:05.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:05.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:05.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:05.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:05.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:05.453: INFO: 
    Jan 16 17:16:07.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:07.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:07.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:07.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
    Jan 16 17:16:07.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:07.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:07.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:07.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:07.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:07.454: INFO: 
    Jan 16 17:16:09.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:09.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:09.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:09.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
    Jan 16 17:16:09.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:09.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:09.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:09.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:09.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:09.453: INFO: 
    Jan 16 17:16:11.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:11.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:11.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:11.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
    Jan 16 17:16:11.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:11.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:11.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:11.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:11.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:11.453: INFO: 
    Jan 16 17:16:13.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:13.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:13.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:13.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
    Jan 16 17:16:13.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:13.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:13.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:13.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:13.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:13.454: INFO: 
    Jan 16 17:16:15.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:15.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:15.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:15.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
    Jan 16 17:16:15.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:15.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:15.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:15.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:15.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:15.453: INFO: 
    Jan 16 17:16:17.464: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:17.464: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:17.464: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:17.464: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
    Jan 16 17:16:17.464: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:17.464: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:17.464: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:17.464: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:17.464: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:17.464: INFO: 
    Jan 16 17:16:19.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:19.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:19.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:19.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
    Jan 16 17:16:19.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:19.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:19.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:19.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:19.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:19.453: INFO: 
    Jan 16 17:16:21.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:21.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:21.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:21.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
    Jan 16 17:16:21.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:21.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:21.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:21.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:21.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:21.452: INFO: 
    Jan 16 17:16:23.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:23.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:23.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:23.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
    Jan 16 17:16:23.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:23.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:23.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:23.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:23.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:23.452: INFO: 
    Jan 16 17:16:25.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:25.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:25.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:25.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
    Jan 16 17:16:25.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:25.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:25.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:25.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:25.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:25.455: INFO: 
    Jan 16 17:16:27.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:27.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:27.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:27.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
    Jan 16 17:16:27.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:27.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:27.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:27.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:27.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:27.453: INFO: 
    Jan 16 17:16:29.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:29.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:29.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:29.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
    Jan 16 17:16:29.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:29.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:29.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:29.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:29.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:29.455: INFO: 
    Jan 16 17:16:31.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:31.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:31.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:31.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
    Jan 16 17:16:31.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:31.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:31.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:31.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:31.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:31.454: INFO: 
    Jan 16 17:16:33.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:33.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:33.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:33.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
    Jan 16 17:16:33.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:33.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:33.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:33.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:33.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:33.455: INFO: 
    Jan 16 17:16:35.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:35.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:35.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:35.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
    Jan 16 17:16:35.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:35.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:35.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:35.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:35.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:35.455: INFO: 
    Jan 16 17:16:37.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:37.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:37.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:37.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
    Jan 16 17:16:37.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:37.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:37.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:37.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:37.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:37.455: INFO: 
    Jan 16 17:16:39.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:39.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:39.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:39.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
    Jan 16 17:16:39.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:39.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:39.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:39.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:39.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:39.454: INFO: 
    Jan 16 17:16:41.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:41.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:41.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:41.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
    Jan 16 17:16:41.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:41.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:41.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:41.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:41.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:41.455: INFO: 
    Jan 16 17:16:43.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:43.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:43.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:43.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
    Jan 16 17:16:43.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:43.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:43.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:43.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:43.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:43.453: INFO: 
    Jan 16 17:16:45.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:45.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:45.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:45.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
    Jan 16 17:16:45.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:45.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:45.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:45.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:45.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:45.453: INFO: 
    Jan 16 17:16:47.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:47.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:47.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:47.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
    Jan 16 17:16:47.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:47.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:47.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:47.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:47.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:47.454: INFO: 
    Jan 16 17:16:49.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:49.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:49.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:49.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
    Jan 16 17:16:49.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:49.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:49.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:49.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:49.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:49.456: INFO: 
    Jan 16 17:16:51.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:51.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:51.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:51.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
    Jan 16 17:16:51.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:51.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:51.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:51.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:51.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:51.452: INFO: 
    Jan 16 17:16:53.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:53.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:53.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:53.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
    Jan 16 17:16:53.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:53.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:53.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:53.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:53.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:53.455: INFO: 
    Jan 16 17:16:55.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:55.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:55.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:55.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
    Jan 16 17:16:55.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:55.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:55.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:55.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:55.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:55.454: INFO: 
    Jan 16 17:16:57.474: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:57.474: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:57.474: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:57.474: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
    Jan 16 17:16:57.474: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:57.474: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:57.474: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:57.474: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:57.474: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:57.474: INFO: 
    Jan 16 17:16:59.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:59.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:59.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:16:59.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
    Jan 16 17:16:59.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:16:59.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:16:59.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:59.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:16:59.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:16:59.455: INFO: 
    Jan 16 17:17:01.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:01.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:01.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:01.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
    Jan 16 17:17:01.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:01.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:01.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:01.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:01.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:01.457: INFO: 
    Jan 16 17:17:03.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:03.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:03.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:03.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
    Jan 16 17:17:03.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:03.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:03.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:03.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:03.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:03.454: INFO: 
    Jan 16 17:17:05.462: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:05.462: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:05.462: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:05.462: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
    Jan 16 17:17:05.462: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:05.462: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:05.462: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:05.462: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:05.462: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:05.462: INFO: 
    Jan 16 17:17:07.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:07.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:07.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:07.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
    Jan 16 17:17:07.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:07.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:07.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:07.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:07.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:07.457: INFO: 
    Jan 16 17:17:09.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:09.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:09.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:09.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
    Jan 16 17:17:09.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:09.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:09.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:09.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:09.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:09.454: INFO: 
    Jan 16 17:17:11.460: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:11.460: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:11.460: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:11.460: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
    Jan 16 17:17:11.460: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:11.460: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:11.460: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:11.460: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:11.460: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:11.460: INFO: 
    Jan 16 17:17:13.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:13.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:13.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:13.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
    Jan 16 17:17:13.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:13.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:13.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:13.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:13.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:13.453: INFO: 
    Jan 16 17:17:15.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:15.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:15.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:15.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
    Jan 16 17:17:15.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:15.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:15.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:15.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:15.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:15.455: INFO: 
    Jan 16 17:17:17.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:17.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:17.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:17.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
    Jan 16 17:17:17.458: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:17.458: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:17.458: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:17.458: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:17.458: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:17.458: INFO: 
    Jan 16 17:17:19.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:19.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:19.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:19.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
    Jan 16 17:17:19.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:19.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:19.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:19.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:19.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:19.454: INFO: 
    Jan 16 17:17:21.451: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:21.451: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:21.451: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:21.451: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
    Jan 16 17:17:21.451: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:21.451: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:21.451: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:21.451: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:21.451: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:21.451: INFO: 
    Jan 16 17:17:23.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:23.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:23.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:23.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
    Jan 16 17:17:23.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:23.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:23.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:23.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:23.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:23.453: INFO: 
    Jan 16 17:17:25.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:25.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:25.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:25.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
    Jan 16 17:17:25.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:25.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:25.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:25.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:25.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:25.454: INFO: 
    Jan 16 17:17:27.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:27.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:27.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:27.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
    Jan 16 17:17:27.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:27.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:27.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:27.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:27.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:27.456: INFO: 
    Jan 16 17:17:29.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:29.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:29.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:29.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
    Jan 16 17:17:29.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:29.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:29.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:29.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:29.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:29.454: INFO: 
    Jan 16 17:17:31.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:31.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:31.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:31.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
    Jan 16 17:17:31.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:31.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:31.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:31.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:31.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:31.455: INFO: 
    Jan 16 17:17:33.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:33.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:33.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:33.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
    Jan 16 17:17:33.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:33.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:33.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:33.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:33.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:33.453: INFO: 
    Jan 16 17:17:35.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:35.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:35.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:35.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
    Jan 16 17:17:35.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:35.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:35.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:35.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:35.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:35.456: INFO: 
    Jan 16 17:17:37.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:37.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:37.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:37.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
    Jan 16 17:17:37.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:37.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:37.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:37.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:37.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:37.453: INFO: 
    Jan 16 17:17:39.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:39.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:39.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:39.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
    Jan 16 17:17:39.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:39.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:39.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:39.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:39.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:39.455: INFO: 
    Jan 16 17:17:41.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:41.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:41.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:41.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
    Jan 16 17:17:41.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:41.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:41.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:41.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:41.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:41.455: INFO: 
    Jan 16 17:17:43.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:43.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:43.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:43.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
    Jan 16 17:17:43.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:43.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:43.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:43.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:43.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:43.453: INFO: 
    Jan 16 17:17:45.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:45.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:45.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:45.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
    Jan 16 17:17:45.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:45.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:45.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:45.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:45.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:45.453: INFO: 
    Jan 16 17:17:47.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:47.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:47.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:47.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
    Jan 16 17:17:47.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:47.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:47.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:47.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:47.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:47.453: INFO: 
    Jan 16 17:17:49.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:49.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:49.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:49.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
    Jan 16 17:17:49.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:49.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:49.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:49.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:49.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:49.455: INFO: 
    Jan 16 17:17:51.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:51.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:51.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:51.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
    Jan 16 17:17:51.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:51.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:51.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:51.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:51.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:51.454: INFO: 
    Jan 16 17:17:53.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:53.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:53.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:53.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
    Jan 16 17:17:53.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:53.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:53.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:53.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:53.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:53.454: INFO: 
    Jan 16 17:17:55.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:55.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:55.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:55.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
    Jan 16 17:17:55.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:55.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:55.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:55.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:55.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:55.455: INFO: 
    Jan 16 17:17:57.459: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:57.459: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:57.459: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:57.459: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
    Jan 16 17:17:57.459: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:57.459: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:57.459: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:57.459: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:57.459: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:57.459: INFO: 
    Jan 16 17:17:59.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:59.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:59.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:17:59.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
    Jan 16 17:17:59.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:17:59.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:17:59.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:59.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:17:59.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:17:59.453: INFO: 
    Jan 16 17:18:01.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:01.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:01.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:01.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
    Jan 16 17:18:01.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:18:01.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:18:01.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:01.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:01.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:18:01.455: INFO: 
    Jan 16 17:18:03.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:03.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:03.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:03.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
    Jan 16 17:18:03.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:18:03.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:18:03.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:03.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:03.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:18:03.453: INFO: 
    Jan 16 17:18:05.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:05.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:05.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:05.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
    Jan 16 17:18:05.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:18:05.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:18:05.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:05.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:05.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:18:05.453: INFO: 
    Jan 16 17:18:07.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:07.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:07.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:07.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
    Jan 16 17:18:07.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:18:07.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:18:07.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:07.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:07.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:18:07.455: INFO: 
    Jan 16 17:18:09.457: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:09.457: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:09.457: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:09.457: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
    Jan 16 17:18:09.457: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:18:09.457: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:18:09.457: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:09.457: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:09.457: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:18:09.457: INFO: 
    Jan 16 17:18:11.456: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:11.456: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:11.456: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:11.456: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
    Jan 16 17:18:11.456: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:18:11.456: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:18:11.456: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:11.456: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:11.456: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:18:11.456: INFO: 
    Jan 16 17:18:13.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:13.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:13.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:13.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
    Jan 16 17:18:13.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:18:13.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:18:13.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:13.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:13.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:18:13.453: INFO: 
    Jan 16 17:18:15.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:15.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:15.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:15.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
    Jan 16 17:18:15.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:18:15.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:18:15.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:15.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:15.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:18:15.453: INFO: 
    Jan 16 17:18:17.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:17.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:17.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:17.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
    Jan 16 17:18:17.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:18:17.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:18:17.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:17.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:17.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:18:17.453: INFO: 
    Jan 16 17:18:19.454: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:19.454: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:19.454: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:19.454: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
    Jan 16 17:18:19.454: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:18:19.454: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:18:19.454: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:19.454: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:19.454: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:18:19.454: INFO: 
    Jan 16 17:18:21.452: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:21.452: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:21.452: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:21.452: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
    Jan 16 17:18:21.452: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:18:21.452: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:18:21.452: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:21.452: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:21.452: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:18:21.452: INFO: 
    Jan 16 17:18:23.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:23.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:23.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:23.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
    Jan 16 17:18:23.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:18:23.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:18:23.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:23.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:23.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:18:23.455: INFO: 
    Jan 16 17:18:25.453: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:25.453: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:25.453: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:25.453: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
    Jan 16 17:18:25.453: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:18:25.453: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:18:25.453: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:25.453: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:25.453: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:18:25.453: INFO: 
    Jan 16 17:18:27.455: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:27.455: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:27.455: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:27.455: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
    Jan 16 17:18:27.455: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:18:27.455: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:18:27.455: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:27.455: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:27.455: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  }]
    Jan 16 17:18:27.455: INFO: 
    Jan 16 17:18:29.464: INFO: The status of Pod kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:29.464: INFO: The status of Pod kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:29.464: INFO: The status of Pod kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Jan 16 17:18:29.464: INFO: 11 / 14 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
    Jan 16 17:18:29.464: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Jan 16 17:18:29.464: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Jan 16 17:18:29.464: INFO: kube-apiserver-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:29.464: INFO: kube-controller-manager-capz-conf-vmxw18-control-plane-kxjwf  capz-conf-vmxw18-control-plane-kxjwf  Pending         []
    Jan 16 17:18:29.464: INFO: kube-scheduler-capz-conf-vmxw18-control-plane-kxjwf           capz-conf-vmxw18-control-plane-kxjwf  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC ContainersNotReady containers with unready status: [kube-scheduler]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2023-01-16 17:10:16 +0000 UTC Contain

PR	mpatlasov: Stop reporting volume limits for migrated in-tree drivers in Node object
Result	FAILURE
Tests	1 failed / 2 succeeded
Started	2023-01-16 16:35
Elapsed	56m11s
Revision	47b72ed5591e8766ff4f4889c0fa4aa3b9b90711
Refs	115040

PR #115040 pull-kubernetes-e2e-capz-conformance #1615024245685882880

Test Failures

capz-e2e [It] Conformance Tests conformance-tests 23m59s

Passed

Skipped

Error lines from build-log.txt