This job view page is being replaced by Spyglass soon. Check out the new job view.
PRpohly: e2e: ginkgo timeouts: use context provided by ginkgo
ResultFAILURE
Tests 1 failed / 0 succeeded
Started2022-11-13 19:56
Elapsed1h4m
Revisionc40350cb7ecf884112940b235205ba723bef32ee
Refs 112923

Test Failures


capz-e2e Conformance Tests conformance-tests 30m0s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sConformance\sTests\sconformance\-tests$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:99
Unexpected error:
    <*errors.withStack | 0xc000be1920>: {
        error: <*errors.withMessage | 0xc001ea0420>{
            cause: <*errors.errorString | 0xc001264130>{
                s: "error container run failed with exit code 1",
            },
            msg: "Unable to run conformance tests",
        },
        stack: [0x2eef258, 0x32e7387, 0x1876cf7, 0x32e7153, 0x14384c5, 0x14379bc, 0x187855c, 0x1879571, 0x1878f65, 0x18785fb, 0x187e889, 0x187e272, 0x188ab71, 0x188a896, 0x1889ee5, 0x188c5a5, 0x1899e09, 0x1899c1e, 0x32ec2f8, 0x148dc2b, 0x13c57e1],
    }
    Unable to run conformance tests: error container run failed with exit code 1
occurred
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:232
				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid


Show 24 Skipped Tests

Error lines from build-log.txt

... skipping 115 lines ...
/home/prow/go/src/k8s.io/kubernetes /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   138  100   138    0     0   5520      0 --:--:-- --:--:-- --:--:--  5520

100    32  100    32    0     0    390      0 --:--:-- --:--:-- --:--:--   390
Error response from daemon: manifest for capzci.azurecr.io/kube-apiserver:v1.26.0-beta.0.76_b8873e9b5f48d9 not found: manifest unknown: manifest tagged by "v1.26.0-beta.0.76_b8873e9b5f48d9" is not found
Building Kubernetes
make: Entering directory '/home/prow/go/src/k8s.io/kubernetes'
+++ [1113 19:57:33] Verifying Prerequisites....
+++ [1113 19:57:33] Building Docker image kube-build:build-60ae33e3b2-5-v1.25.0-go1.19.3-bullseye.0
+++ [1113 20:00:30] Creating data container kube-build-data-60ae33e3b2-5-v1.25.0-go1.19.3-bullseye.0
+++ [1113 20:00:51] Syncing sources to container
... skipping 738 lines ...
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:99
[BeforeEach] Conformance Tests
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:55
INFO: Cluster name is capz-conf-m00n9c
STEP: Creating namespace "capz-conf-m00n9c" for hosting the cluster
Nov 13 20:30:35.370: INFO: starting to create namespace for hosting the "capz-conf-m00n9c" test spec
2022/11/13 20:30:35 failed trying to get namespace (capz-conf-m00n9c):namespaces "capz-conf-m00n9c" not found
INFO: Creating namespace capz-conf-m00n9c
INFO: Creating event watcher for namespace "capz-conf-m00n9c"
[Measure] conformance-tests
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:99
INFO: Creating the workload cluster with name "capz-conf-m00n9c" using the "conformance-presubmit-artifacts-windows-containerd" template (Kubernetes v1.26.0-beta.0.65+8e48df13531802, 1 control-plane machines, 0 worker machines)
INFO: Getting the cluster template yaml
... skipping 41 lines ...
====================================================
Random Seed: 1668372011 - will randomize all specs

Will run 339 of 7066 specs
Running in parallel across 4 processes
------------------------------
[SynchronizedBeforeSuite] [FAILED] [606.197 seconds]

[SynchronizedBeforeSuite] 
test/e2e/e2e.go:77

  Begin Captured GinkgoWriter Output >>
    [SynchronizedBeforeSuite] TOP-LEVEL
      test/e2e/e2e.go:77
    Nov 13 20:40:12.087: INFO: >>> kubeConfig: /tmp/kubeconfig
    Nov 13 20:40:12.093: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
    Nov 13 20:40:12.295: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
    Nov 13 20:40:12.447: INFO: The status of Pod calico-node-windows-k2x9h is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:12.447: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:12.447: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:12.447: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:12.447: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
    Nov 13 20:40:12.447: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:12.447: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:12.447: INFO: calico-node-windows-k2x9h                                     capz-conf-fs5d4                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:39:09 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:40:08 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:40:08 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:38:38 +0000 UTC  }]
    Nov 13 20:40:12.447: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:12.447: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:12.447: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:12.447: INFO: 
    Nov 13 20:40:14.582: INFO: The status of Pod calico-node-windows-k2x9h is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:14.582: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:14.582: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:14.582: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:14.582: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
    Nov 13 20:40:14.582: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:14.582: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:14.582: INFO: calico-node-windows-k2x9h                                     capz-conf-fs5d4                       Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:39:09 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:40:08 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:40:08 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:38:38 +0000 UTC  }]
    Nov 13 20:40:14.582: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:14.582: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:14.582: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:14.582: INFO: 
    Nov 13 20:40:16.583: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:16.583: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:16.583: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:16.583: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
    Nov 13 20:40:16.583: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:16.583: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:16.583: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:16.583: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:16.583: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:16.583: INFO: 
    Nov 13 20:40:18.579: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:18.580: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:18.580: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:18.580: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
    Nov 13 20:40:18.580: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:18.580: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:18.580: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:18.580: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:18.580: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:18.580: INFO: 
    Nov 13 20:40:20.588: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:20.588: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:20.588: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:20.588: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
    Nov 13 20:40:20.588: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:20.588: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:20.588: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:20.588: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:20.588: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:20.588: INFO: 
    Nov 13 20:40:22.580: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:22.580: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:22.580: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:22.580: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
    Nov 13 20:40:22.580: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:22.580: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:22.580: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:22.580: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:22.580: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:22.580: INFO: 
    Nov 13 20:40:24.588: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:24.588: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:24.588: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:24.588: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
    Nov 13 20:40:24.588: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:24.588: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:24.588: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:24.588: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:24.588: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:24.588: INFO: 
    Nov 13 20:40:26.584: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:26.584: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:26.584: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:26.584: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
    Nov 13 20:40:26.584: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:26.584: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:26.584: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:26.584: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:26.584: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:26.584: INFO: 
    Nov 13 20:40:28.580: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:28.580: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:28.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:28.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
    Nov 13 20:40:28.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:28.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:28.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:28.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:28.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:28.581: INFO: 
    Nov 13 20:40:30.584: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:30.585: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:30.585: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:30.585: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
    Nov 13 20:40:30.585: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:30.585: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:30.585: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:30.585: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:30.585: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:30.585: INFO: 
    Nov 13 20:40:32.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:32.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:32.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:32.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
    Nov 13 20:40:32.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:32.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:32.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:32.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:32.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:32.581: INFO: 
    Nov 13 20:40:34.582: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:34.582: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:34.582: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:34.582: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
    Nov 13 20:40:34.582: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:34.582: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:34.582: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:34.582: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:34.582: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:34.582: INFO: 
    Nov 13 20:40:36.585: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:36.585: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:36.585: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:36.585: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
    Nov 13 20:40:36.585: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:36.585: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:36.585: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:36.585: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:36.585: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:36.585: INFO: 
    Nov 13 20:40:38.587: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:38.587: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:38.587: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:38.587: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
    Nov 13 20:40:38.587: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:38.587: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:38.587: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:38.587: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:38.587: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:38.587: INFO: 
    Nov 13 20:40:40.579: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:40.579: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:40.579: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:40.579: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
    Nov 13 20:40:40.579: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:40.579: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:40.579: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:40.579: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:40.579: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:40.579: INFO: 
    Nov 13 20:40:42.585: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:42.585: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:42.585: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:42.585: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
    Nov 13 20:40:42.585: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:42.585: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:42.585: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:42.585: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:42.585: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:42.585: INFO: 
    Nov 13 20:40:44.586: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:44.586: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:44.586: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:44.586: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
    Nov 13 20:40:44.586: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:44.586: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:44.586: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:44.586: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:44.586: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:44.586: INFO: 
    Nov 13 20:40:46.597: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:46.597: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:46.597: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:46.597: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
    Nov 13 20:40:46.597: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:46.597: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:46.597: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:46.597: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:46.597: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:46.597: INFO: 
    Nov 13 20:40:48.585: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:48.585: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:48.585: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:48.586: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
    Nov 13 20:40:48.586: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:48.586: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:48.586: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:48.586: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:48.594: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:48.594: INFO: 
    Nov 13 20:40:50.582: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:50.582: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:50.582: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:50.582: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
    Nov 13 20:40:50.582: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:50.582: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:50.582: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:50.582: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:50.583: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:50.583: INFO: 
    Nov 13 20:40:52.580: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:52.580: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:52.580: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:52.580: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
    Nov 13 20:40:52.580: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:52.580: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:52.580: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:52.580: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:52.580: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:52.580: INFO: 
    Nov 13 20:40:54.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:54.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:54.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:54.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
    Nov 13 20:40:54.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:54.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:54.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:54.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:54.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:54.581: INFO: 
    Nov 13 20:40:56.585: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:56.585: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:56.585: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:56.585: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
    Nov 13 20:40:56.585: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:56.585: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:56.585: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:56.585: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:56.585: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:56.585: INFO: 
    Nov 13 20:40:58.579: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:58.579: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:58.579: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:40:58.579: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
    Nov 13 20:40:58.579: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:40:58.579: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:40:58.579: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:58.579: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:58.579: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:40:58.579: INFO: 
    Nov 13 20:41:00.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:00.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:00.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:00.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
    Nov 13 20:41:00.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:00.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:00.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:00.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:00.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:00.581: INFO: 
    Nov 13 20:41:02.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:02.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:02.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:02.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
    Nov 13 20:41:02.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:02.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:02.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:02.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:02.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:02.581: INFO: 
    Nov 13 20:41:04.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:04.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:04.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:04.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
    Nov 13 20:41:04.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:04.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:04.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:04.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:04.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:04.581: INFO: 
    Nov 13 20:41:06.579: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:06.579: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:06.579: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:06.579: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
    Nov 13 20:41:06.579: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:06.579: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:06.579: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:06.579: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:06.579: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:06.579: INFO: 
    Nov 13 20:41:08.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:08.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:08.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:08.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
    Nov 13 20:41:08.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:08.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:08.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:08.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:08.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:08.581: INFO: 
    Nov 13 20:41:10.579: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:10.579: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:10.579: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:10.579: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
    Nov 13 20:41:10.579: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:10.579: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:10.579: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:10.579: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:10.579: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:10.579: INFO: 
    Nov 13 20:41:12.582: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:12.582: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:12.582: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:12.582: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
    Nov 13 20:41:12.582: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:12.582: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:12.582: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:12.582: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:12.582: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:12.582: INFO: 
    Nov 13 20:41:14.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:14.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:14.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:14.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
    Nov 13 20:41:14.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:14.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:14.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:14.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:14.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:14.581: INFO: 
    Nov 13 20:41:16.580: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:16.580: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:16.580: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:16.580: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
    Nov 13 20:41:16.580: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:16.580: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:16.580: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:16.580: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:16.580: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:16.580: INFO: 
    Nov 13 20:41:18.579: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:18.579: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:18.579: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:18.579: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
    Nov 13 20:41:18.579: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:18.579: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:18.579: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:18.579: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:18.579: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:18.579: INFO: 
    Nov 13 20:41:20.582: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:20.582: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:20.582: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:20.582: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
    Nov 13 20:41:20.582: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:20.583: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:20.583: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:20.583: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:20.583: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:20.583: INFO: 
    Nov 13 20:41:22.583: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:22.583: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:22.583: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:22.583: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
    Nov 13 20:41:22.583: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:22.583: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:22.583: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:22.583: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:22.583: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:22.583: INFO: 
    Nov 13 20:41:24.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:24.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:24.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:24.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
    Nov 13 20:41:24.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:24.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:24.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:24.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:24.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:24.581: INFO: 
    Nov 13 20:41:26.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:26.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:26.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:26.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
    Nov 13 20:41:26.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:26.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:26.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:26.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:26.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:26.581: INFO: 
    Nov 13 20:41:28.583: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:28.583: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:28.583: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:28.583: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
    Nov 13 20:41:28.583: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:28.583: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:28.583: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:28.583: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:28.583: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:28.583: INFO: 
    Nov 13 20:41:30.583: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:30.583: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:30.583: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:30.583: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
    Nov 13 20:41:30.583: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:30.583: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:30.583: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:30.583: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:30.583: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:30.583: INFO: 
    Nov 13 20:41:32.585: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:32.585: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:32.585: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:32.585: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
    Nov 13 20:41:32.585: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:32.585: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:32.585: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:32.585: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:32.585: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:32.585: INFO: 
    Nov 13 20:41:34.587: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:34.587: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:34.588: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:34.588: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
    Nov 13 20:41:34.588: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:34.588: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:34.588: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:34.588: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:34.588: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:34.588: INFO: 
    Nov 13 20:41:36.586: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:36.586: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:36.586: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:36.586: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
    Nov 13 20:41:36.586: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:36.586: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:36.586: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:36.586: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:36.586: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:36.586: INFO: 
    Nov 13 20:41:38.583: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:38.583: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:38.583: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:38.583: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
    Nov 13 20:41:38.583: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:38.583: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:38.583: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:38.583: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:38.583: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:38.583: INFO: 
    Nov 13 20:41:40.592: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:40.592: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:40.592: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:40.592: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
    Nov 13 20:41:40.592: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:40.592: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:40.592: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:40.592: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:40.592: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:40.592: INFO: 
    Nov 13 20:41:42.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:42.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:42.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:42.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
    Nov 13 20:41:42.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:42.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:42.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:42.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:42.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:42.581: INFO: 
    Nov 13 20:41:44.579: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:44.579: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:44.579: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:44.579: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
    Nov 13 20:41:44.579: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:44.579: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:44.579: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:44.579: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:44.579: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:44.579: INFO: 
    Nov 13 20:41:46.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:46.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:46.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:46.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
    Nov 13 20:41:46.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:46.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:46.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:46.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:46.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:46.581: INFO: 
    Nov 13 20:41:48.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:48.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:48.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:48.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
    Nov 13 20:41:48.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:48.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:48.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:48.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:48.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:48.581: INFO: 
    Nov 13 20:41:50.580: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:50.580: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:50.580: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:50.580: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
    Nov 13 20:41:50.580: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:50.580: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:50.580: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:50.580: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:50.580: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:50.580: INFO: 
    Nov 13 20:41:52.586: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:52.586: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:52.586: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:52.586: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
    Nov 13 20:41:52.586: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:52.586: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:52.586: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:52.586: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:52.586: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:52.586: INFO: 
    Nov 13 20:41:54.584: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:54.584: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:54.584: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:54.584: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
    Nov 13 20:41:54.584: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:54.584: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:54.584: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:54.584: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:54.584: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:54.584: INFO: 
    Nov 13 20:41:56.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:56.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:56.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:56.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
    Nov 13 20:41:56.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:56.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:56.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:56.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:56.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:56.581: INFO: 
    Nov 13 20:41:58.579: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:58.579: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:58.579: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:41:58.579: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
    Nov 13 20:41:58.579: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:41:58.579: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:41:58.579: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:58.579: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:58.579: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:41:58.579: INFO: 
    Nov 13 20:42:00.582: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:00.582: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:00.582: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:00.582: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
    Nov 13 20:42:00.582: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:00.582: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:00.582: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:00.582: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:00.582: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:00.582: INFO: 
    Nov 13 20:42:02.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:02.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:02.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:02.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
    Nov 13 20:42:02.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:02.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:02.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:02.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:02.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:02.581: INFO: 
    Nov 13 20:42:04.584: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:04.584: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:04.584: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:04.584: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
    Nov 13 20:42:04.584: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:04.584: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:04.584: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:04.584: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:04.584: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:04.584: INFO: 
    Nov 13 20:42:06.582: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:06.582: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:06.582: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:06.582: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
    Nov 13 20:42:06.582: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:06.582: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:06.582: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:06.582: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:06.582: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:06.582: INFO: 
    Nov 13 20:42:08.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:08.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:08.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:08.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
    Nov 13 20:42:08.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:08.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:08.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:08.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:08.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:08.581: INFO: 
    Nov 13 20:42:10.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:10.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:10.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:10.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
    Nov 13 20:42:10.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:10.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:10.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:10.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:10.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:10.581: INFO: 
    Nov 13 20:42:12.582: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:12.582: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:12.582: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:12.582: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
    Nov 13 20:42:12.582: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:12.582: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:12.582: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:12.582: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:12.582: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:12.582: INFO: 
    Nov 13 20:42:14.580: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:14.580: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:14.580: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:14.580: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
    Nov 13 20:42:14.580: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:14.580: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:14.580: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:14.580: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:14.580: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:14.580: INFO: 
    Nov 13 20:42:16.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:16.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:16.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:16.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
    Nov 13 20:42:16.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:16.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:16.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:16.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:16.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:16.577: INFO: 
    Nov 13 20:42:18.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:18.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:18.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:18.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
    Nov 13 20:42:18.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:18.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:18.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:18.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:18.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:18.581: INFO: 
    Nov 13 20:42:20.579: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:20.579: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:20.579: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:20.579: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
    Nov 13 20:42:20.579: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:20.579: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:20.579: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:20.579: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:20.579: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:20.579: INFO: 
    Nov 13 20:42:22.579: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:22.579: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:22.579: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:22.579: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
    Nov 13 20:42:22.579: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:22.579: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:22.579: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:22.579: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:22.579: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:22.579: INFO: 
    Nov 13 20:42:24.583: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:24.583: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:24.583: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:24.583: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
    Nov 13 20:42:24.583: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:24.583: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:24.583: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:24.583: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:24.583: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:24.583: INFO: 
    Nov 13 20:42:26.580: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:26.580: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:26.580: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:26.580: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
    Nov 13 20:42:26.580: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:26.580: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:26.580: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:26.580: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:26.580: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:26.580: INFO: 
    Nov 13 20:42:28.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:28.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:28.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:28.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
    Nov 13 20:42:28.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:28.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:28.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:28.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:28.578: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:28.578: INFO: 
    Nov 13 20:42:30.584: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:30.584: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:30.584: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:30.584: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
    Nov 13 20:42:30.584: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:30.584: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:30.584: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:30.584: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:30.584: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:30.584: INFO: 
    Nov 13 20:42:32.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:32.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:32.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:32.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
    Nov 13 20:42:32.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:32.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:32.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:32.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:32.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:32.581: INFO: 
    Nov 13 20:42:34.578: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:34.578: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:34.578: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:34.578: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
    Nov 13 20:42:34.579: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:34.579: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:34.579: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:34.579: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:34.579: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:34.579: INFO: 
    Nov 13 20:42:36.582: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:36.582: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:36.582: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:36.582: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
    Nov 13 20:42:36.582: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:36.582: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:36.582: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:36.582: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:36.582: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:36.582: INFO: 
    Nov 13 20:42:38.580: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:38.580: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:38.580: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:38.580: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
    Nov 13 20:42:38.580: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:38.580: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:38.580: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:38.580: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:38.580: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:38.580: INFO: 
    Nov 13 20:42:40.582: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:40.582: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:40.582: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:40.582: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
    Nov 13 20:42:40.582: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:40.582: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:40.582: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:40.582: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:40.582: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:40.582: INFO: 
    Nov 13 20:42:42.579: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:42.579: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:42.579: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:42.579: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
    Nov 13 20:42:42.579: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:42.579: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:42.579: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:42.579: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:42.579: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:42.579: INFO: 
    Nov 13 20:42:44.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:44.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:44.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:44.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
    Nov 13 20:42:44.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:44.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:44.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:44.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:44.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:44.581: INFO: 
    Nov 13 20:42:46.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:46.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:46.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:46.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
    Nov 13 20:42:46.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:46.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:46.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:46.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:46.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:46.581: INFO: 
    Nov 13 20:42:48.578: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:48.578: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:48.578: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:48.578: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
    Nov 13 20:42:48.578: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:48.578: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:48.578: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:48.578: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:48.578: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:48.578: INFO: 
    Nov 13 20:42:50.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:50.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:50.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:50.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
    Nov 13 20:42:50.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:50.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:50.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:50.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:50.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:50.581: INFO: 
    Nov 13 20:42:52.694: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:52.694: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:52.694: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:52.694: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
    Nov 13 20:42:52.694: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:52.694: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:52.694: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:52.694: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:52.694: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:52.694: INFO: 
    Nov 13 20:42:54.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:54.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:54.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:54.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
    Nov 13 20:42:54.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:54.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:54.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:54.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:54.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:54.581: INFO: 
    Nov 13 20:42:56.580: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:56.580: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:56.580: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:56.580: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
    Nov 13 20:42:56.580: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:56.580: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:56.580: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:56.580: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:56.580: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:56.580: INFO: 
    Nov 13 20:42:58.579: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:58.579: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:58.579: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:42:58.579: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
    Nov 13 20:42:58.579: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:42:58.579: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:42:58.579: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:58.579: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:58.579: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:42:58.579: INFO: 
    Nov 13 20:43:00.580: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:00.580: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:00.580: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:00.580: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
    Nov 13 20:43:00.580: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:00.580: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:00.580: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:00.580: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:00.580: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:00.580: INFO: 
    Nov 13 20:43:02.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:02.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:02.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:02.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
    Nov 13 20:43:02.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:02.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:02.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:02.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:02.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:02.581: INFO: 
    Nov 13 20:43:04.578: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:04.578: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:04.578: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:04.578: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
    Nov 13 20:43:04.578: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:04.578: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:04.578: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:04.578: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:04.578: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:04.578: INFO: 
    Nov 13 20:43:06.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:06.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:06.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:06.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
    Nov 13 20:43:06.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:06.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:06.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:06.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:06.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:06.577: INFO: 
    Nov 13 20:43:08.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:08.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:08.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:08.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
    Nov 13 20:43:08.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:08.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:08.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:08.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:08.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:08.577: INFO: 
    Nov 13 20:43:10.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:10.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:10.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:10.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
    Nov 13 20:43:10.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:10.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:10.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:10.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:10.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:10.576: INFO: 
    Nov 13 20:43:12.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:12.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:12.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:12.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
    Nov 13 20:43:12.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:12.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:12.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:12.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:12.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:12.575: INFO: 
    Nov 13 20:43:14.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:14.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:14.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:14.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
    Nov 13 20:43:14.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:14.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:14.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:14.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:14.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:14.575: INFO: 
    Nov 13 20:43:16.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:16.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:16.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:16.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
    Nov 13 20:43:16.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:16.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:16.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:16.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:16.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:16.576: INFO: 
    Nov 13 20:43:18.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:18.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:18.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:18.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
    Nov 13 20:43:18.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:18.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:18.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:18.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:18.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:18.577: INFO: 
    Nov 13 20:43:20.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:20.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:20.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:20.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
    Nov 13 20:43:20.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:20.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:20.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:20.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:20.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:20.575: INFO: 
    Nov 13 20:43:22.578: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:22.578: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:22.578: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:22.578: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
    Nov 13 20:43:22.578: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:22.578: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:22.578: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:22.578: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:22.578: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:22.578: INFO: 
    Nov 13 20:43:24.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:24.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:24.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:24.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
    Nov 13 20:43:24.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:24.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:24.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:24.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:24.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:24.575: INFO: 
    Nov 13 20:43:26.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:26.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:26.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:26.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
    Nov 13 20:43:26.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:26.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:26.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:26.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:26.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:26.575: INFO: 
    Nov 13 20:43:28.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:28.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:28.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:28.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
    Nov 13 20:43:28.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:28.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:28.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:28.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:28.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:28.575: INFO: 
    Nov 13 20:43:30.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:30.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:30.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:30.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
    Nov 13 20:43:30.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:30.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:30.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:30.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:30.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:30.577: INFO: 
    Nov 13 20:43:32.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:32.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:32.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:32.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
    Nov 13 20:43:32.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:32.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:32.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:32.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:32.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:32.574: INFO: 
    Nov 13 20:43:34.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:34.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:34.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:34.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
    Nov 13 20:43:34.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:34.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:34.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:34.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:34.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:34.575: INFO: 
    Nov 13 20:43:36.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:36.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:36.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:36.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
    Nov 13 20:43:36.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:36.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:36.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:36.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:36.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:36.576: INFO: 
    Nov 13 20:43:38.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:38.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:38.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:38.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
    Nov 13 20:43:38.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:38.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:38.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:38.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:38.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:38.574: INFO: 
    Nov 13 20:43:40.578: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:40.578: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:40.578: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:40.578: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
    Nov 13 20:43:40.578: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:40.578: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:40.578: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:40.578: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:40.578: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:40.578: INFO: 
    Nov 13 20:43:42.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:42.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:42.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:42.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
    Nov 13 20:43:42.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:42.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:42.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:42.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:42.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:42.574: INFO: 
    Nov 13 20:43:44.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:44.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:44.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:44.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
    Nov 13 20:43:44.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:44.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:44.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:44.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:44.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:44.576: INFO: 
    Nov 13 20:43:46.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:46.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:46.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:46.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
    Nov 13 20:43:46.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:46.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:46.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:46.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:46.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:46.576: INFO: 
    Nov 13 20:43:48.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:48.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:48.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:48.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
    Nov 13 20:43:48.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:48.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:48.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:48.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:48.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:48.575: INFO: 
    Nov 13 20:43:50.688: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:50.688: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:50.688: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:50.688: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
    Nov 13 20:43:50.688: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:50.688: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:50.688: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:50.688: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:50.688: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:50.688: INFO: 
    Nov 13 20:43:52.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:52.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:52.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:52.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
    Nov 13 20:43:52.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:52.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:52.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:52.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:52.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:52.575: INFO: 
    Nov 13 20:43:54.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:54.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:54.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:54.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
    Nov 13 20:43:54.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:54.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:54.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:54.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:54.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:54.575: INFO: 
    Nov 13 20:43:56.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:56.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:56.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:56.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
    Nov 13 20:43:56.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:56.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:56.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:56.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:56.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:56.575: INFO: 
    Nov 13 20:43:58.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:58.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:58.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:43:58.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
    Nov 13 20:43:58.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:43:58.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:43:58.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:58.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:58.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:43:58.575: INFO: 
    Nov 13 20:44:00.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:00.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:00.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:00.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
    Nov 13 20:44:00.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:00.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:00.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:00.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:00.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:00.575: INFO: 
    Nov 13 20:44:02.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:02.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:02.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:02.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
    Nov 13 20:44:02.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:02.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:02.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:02.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:02.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:02.574: INFO: 
    Nov 13 20:44:04.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:04.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:04.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:04.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
    Nov 13 20:44:04.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:04.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:04.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:04.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:04.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:04.574: INFO: 
    Nov 13 20:44:06.578: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:06.578: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:06.578: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:06.578: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
    Nov 13 20:44:06.578: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:06.578: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:06.578: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:06.578: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:06.578: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:06.578: INFO: 
    Nov 13 20:44:08.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:08.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:08.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:08.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
    Nov 13 20:44:08.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:08.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:08.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:08.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:08.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:08.574: INFO: 
    Nov 13 20:44:10.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:10.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:10.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:10.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
    Nov 13 20:44:10.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:10.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:10.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:10.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:10.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:10.575: INFO: 
    Nov 13 20:44:12.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:12.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:12.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:12.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
    Nov 13 20:44:12.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:12.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:12.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:12.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:12.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:12.575: INFO: 
    Nov 13 20:44:14.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:14.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:14.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:14.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
    Nov 13 20:44:14.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:14.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:14.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:14.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:14.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:14.576: INFO: 
    Nov 13 20:44:16.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:16.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:16.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:16.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
    Nov 13 20:44:16.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:16.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:16.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:16.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:16.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:16.574: INFO: 
    Nov 13 20:44:18.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:18.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:18.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:18.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
    Nov 13 20:44:18.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:18.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:18.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:18.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:18.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:18.575: INFO: 
    Nov 13 20:44:20.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:20.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:20.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:20.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
    Nov 13 20:44:20.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:20.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:20.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:20.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:20.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:20.575: INFO: 
    Nov 13 20:44:22.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:22.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:22.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:22.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
    Nov 13 20:44:22.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:22.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:22.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:22.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:22.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:22.575: INFO: 
    Nov 13 20:44:24.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:24.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:24.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:24.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
    Nov 13 20:44:24.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:24.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:24.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:24.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:24.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:24.574: INFO: 
    Nov 13 20:44:26.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:26.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:26.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:26.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
    Nov 13 20:44:26.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:26.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:26.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:26.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:26.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:26.576: INFO: 
    Nov 13 20:44:28.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:28.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:28.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:28.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
    Nov 13 20:44:28.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:28.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:28.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:28.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:28.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:28.577: INFO: 
    Nov 13 20:44:30.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:30.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:30.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:30.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
    Nov 13 20:44:30.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:30.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:30.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:30.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:30.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:30.575: INFO: 
    Nov 13 20:44:32.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:32.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:32.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:32.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
    Nov 13 20:44:32.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:32.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:32.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:32.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:32.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:32.576: INFO: 
    Nov 13 20:44:34.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:34.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:34.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:34.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
    Nov 13 20:44:34.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:34.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:34.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:34.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:34.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:34.575: INFO: 
    Nov 13 20:44:36.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:36.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:36.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:36.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
    Nov 13 20:44:36.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:36.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:36.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:36.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:36.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:36.574: INFO: 
    Nov 13 20:44:38.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:38.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:38.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:38.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
    Nov 13 20:44:38.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:38.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:38.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:38.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:38.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:38.575: INFO: 
    Nov 13 20:44:40.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:40.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:40.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:40.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
    Nov 13 20:44:40.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:40.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:40.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:40.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:40.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:40.576: INFO: 
    Nov 13 20:44:42.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:42.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:42.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:42.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
    Nov 13 20:44:42.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:42.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:42.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:42.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:42.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:42.575: INFO: 
    Nov 13 20:44:44.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:44.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:44.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:44.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
    Nov 13 20:44:44.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:44.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:44.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:44.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:44.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:44.575: INFO: 
    Nov 13 20:44:46.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:46.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:46.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:46.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
    Nov 13 20:44:46.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:46.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:46.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:46.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:46.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:46.576: INFO: 
    Nov 13 20:44:48.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:48.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:48.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:48.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
    Nov 13 20:44:48.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:48.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:48.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:48.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:48.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:48.574: INFO: 
    Nov 13 20:44:50.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:50.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:50.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:50.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
    Nov 13 20:44:50.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:50.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:50.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:50.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:50.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:50.575: INFO: 
    Nov 13 20:44:52.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:52.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:52.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:52.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
    Nov 13 20:44:52.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:52.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:52.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:52.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:52.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:52.574: INFO: 
    Nov 13 20:44:54.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:54.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:54.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:54.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
    Nov 13 20:44:54.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:54.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:54.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:54.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:54.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:54.575: INFO: 
    Nov 13 20:44:56.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:56.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:56.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:56.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
    Nov 13 20:44:56.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:56.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:56.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:56.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:56.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:56.581: INFO: 
    Nov 13 20:44:58.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:58.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:58.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:44:58.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
    Nov 13 20:44:58.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:44:58.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:44:58.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:58.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:58.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:44:58.576: INFO: 
    Nov 13 20:45:00.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:00.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:00.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:00.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
    Nov 13 20:45:00.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:00.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:00.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:00.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:00.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:00.575: INFO: 
    Nov 13 20:45:02.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:02.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:02.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:02.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
    Nov 13 20:45:02.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:02.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:02.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:02.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:02.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:02.574: INFO: 
    Nov 13 20:45:04.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:04.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:04.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:04.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
    Nov 13 20:45:04.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:04.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:04.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:04.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:04.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:04.575: INFO: 
    Nov 13 20:45:06.583: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:06.583: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:06.583: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:06.583: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
    Nov 13 20:45:06.583: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:06.583: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:06.583: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:06.583: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:06.583: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:06.583: INFO: 
    Nov 13 20:45:08.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:08.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:08.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:08.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
    Nov 13 20:45:08.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:08.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:08.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:08.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:08.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:08.576: INFO: 
    Nov 13 20:45:10.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:10.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:10.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:10.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
    Nov 13 20:45:10.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:10.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:10.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:10.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:10.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:10.576: INFO: 
    Nov 13 20:45:12.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:12.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:12.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:12.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
    Nov 13 20:45:12.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:12.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:12.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:12.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:12.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:12.575: INFO: 
    Nov 13 20:45:14.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:14.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:14.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:14.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
    Nov 13 20:45:14.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:14.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:14.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:14.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:14.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:14.574: INFO: 
    Nov 13 20:45:16.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:16.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:16.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:16.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
    Nov 13 20:45:16.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:16.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:16.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:16.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:16.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:16.576: INFO: 
    Nov 13 20:45:18.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:18.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:18.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:18.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
    Nov 13 20:45:18.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:18.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:18.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:18.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:18.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:18.575: INFO: 
    Nov 13 20:45:20.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:20.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:20.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:20.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
    Nov 13 20:45:20.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:20.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:20.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:20.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:20.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:20.574: INFO: 
    Nov 13 20:45:22.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:22.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:22.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:22.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
    Nov 13 20:45:22.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:22.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:22.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:22.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:22.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:22.575: INFO: 
    Nov 13 20:45:24.582: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:24.582: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:24.582: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:24.582: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
    Nov 13 20:45:24.582: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:24.582: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:24.582: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:24.582: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:24.582: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:24.582: INFO: 
    Nov 13 20:45:26.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:26.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:26.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:26.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
    Nov 13 20:45:26.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:26.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:26.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:26.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:26.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:26.575: INFO: 
    Nov 13 20:45:28.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:28.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:28.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:28.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
    Nov 13 20:45:28.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:28.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:28.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:28.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:28.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:28.575: INFO: 
    Nov 13 20:45:30.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:30.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:30.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:30.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
    Nov 13 20:45:30.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:30.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:30.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:30.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:30.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:30.575: INFO: 
    Nov 13 20:45:32.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:32.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:32.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:32.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
    Nov 13 20:45:32.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:32.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:32.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:32.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:32.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:32.575: INFO: 
    Nov 13 20:45:34.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:34.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:34.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:34.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
    Nov 13 20:45:34.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:34.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:34.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:34.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:34.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:34.574: INFO: 
    Nov 13 20:45:36.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:36.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:36.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:36.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
    Nov 13 20:45:36.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:36.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:36.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:36.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:36.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:36.575: INFO: 
    Nov 13 20:45:38.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:38.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:38.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:38.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
    Nov 13 20:45:38.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:38.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:38.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:38.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:38.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:38.575: INFO: 
    Nov 13 20:45:40.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:40.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:40.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:40.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
    Nov 13 20:45:40.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:40.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:40.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:40.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:40.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:40.574: INFO: 
    Nov 13 20:45:42.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:42.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:42.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:42.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
    Nov 13 20:45:42.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:42.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:42.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:42.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:42.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:42.581: INFO: 
    Nov 13 20:45:44.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:44.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:44.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:44.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
    Nov 13 20:45:44.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:44.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:44.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:44.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:44.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:44.575: INFO: 
    Nov 13 20:45:46.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:46.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:46.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:46.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
    Nov 13 20:45:46.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:46.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:46.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:46.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:46.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:46.575: INFO: 
    Nov 13 20:45:48.582: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:48.582: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:48.582: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:48.582: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
    Nov 13 20:45:48.582: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:48.582: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:48.582: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:48.582: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:48.582: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:48.582: INFO: 
    Nov 13 20:45:50.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:50.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:50.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:50.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
    Nov 13 20:45:50.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:50.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:50.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:50.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:50.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:50.575: INFO: 
    Nov 13 20:45:52.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:52.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:52.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:52.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
    Nov 13 20:45:52.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:52.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:52.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:52.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:52.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:52.575: INFO: 
    Nov 13 20:45:54.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:54.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:54.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:54.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
    Nov 13 20:45:54.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:54.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:54.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:54.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:54.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:54.575: INFO: 
    Nov 13 20:45:56.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:56.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:56.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:56.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
    Nov 13 20:45:56.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:56.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:56.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:56.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:56.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:56.576: INFO: 
    Nov 13 20:45:58.586: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:58.586: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:58.586: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:45:58.586: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
    Nov 13 20:45:58.586: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:45:58.586: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:45:58.586: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:58.586: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:58.586: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:45:58.586: INFO: 
    Nov 13 20:46:00.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:00.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:00.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:00.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
    Nov 13 20:46:00.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:00.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:00.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:00.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:00.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:00.577: INFO: 
    Nov 13 20:46:02.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:02.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:02.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:02.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
    Nov 13 20:46:02.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:02.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:02.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:02.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:02.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:02.576: INFO: 
    Nov 13 20:46:04.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:04.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:04.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:04.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
    Nov 13 20:46:04.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:04.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:04.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:04.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:04.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:04.575: INFO: 
    Nov 13 20:46:06.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:06.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:06.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:06.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
    Nov 13 20:46:06.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:06.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:06.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:06.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:06.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:06.575: INFO: 
    Nov 13 20:46:08.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:08.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:08.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:08.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
    Nov 13 20:46:08.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:08.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:08.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:08.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:08.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:08.574: INFO: 
    Nov 13 20:46:10.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:10.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:10.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:10.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
    Nov 13 20:46:10.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:10.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:10.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:10.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:10.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:10.575: INFO: 
    Nov 13 20:46:12.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:12.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:12.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:12.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
    Nov 13 20:46:12.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:12.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:12.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:12.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:12.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:12.574: INFO: 
    Nov 13 20:46:14.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:14.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:14.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:14.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
    Nov 13 20:46:14.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:14.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:14.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:14.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:14.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:14.574: INFO: 
    Nov 13 20:46:16.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:16.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:16.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:16.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
    Nov 13 20:46:16.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:16.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:16.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:16.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:16.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:16.575: INFO: 
    Nov 13 20:46:18.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:18.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:18.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:18.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
    Nov 13 20:46:18.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:18.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:18.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:18.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:18.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:18.575: INFO: 
    Nov 13 20:46:20.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:20.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:20.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:20.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
    Nov 13 20:46:20.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:20.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:20.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:20.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:20.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:20.574: INFO: 
    Nov 13 20:46:22.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:22.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:22.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:22.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
    Nov 13 20:46:22.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:22.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:22.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:22.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:22.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:22.575: INFO: 
    Nov 13 20:46:24.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:24.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:24.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:24.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
    Nov 13 20:46:24.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:24.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:24.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:24.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:24.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:24.575: INFO: 
    Nov 13 20:46:26.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:26.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:26.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:26.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
    Nov 13 20:46:26.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:26.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:26.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:26.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:26.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:26.575: INFO: 
    Nov 13 20:46:28.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:28.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:28.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:28.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
    Nov 13 20:46:28.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:28.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:28.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:28.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:28.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:28.577: INFO: 
    Nov 13 20:46:30.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:30.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:30.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:30.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
    Nov 13 20:46:30.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:30.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:30.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:30.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:30.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:30.574: INFO: 
    Nov 13 20:46:32.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:32.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:32.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:32.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
    Nov 13 20:46:32.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:32.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:32.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:32.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:32.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:32.575: INFO: 
    Nov 13 20:46:34.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:34.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:34.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:34.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
    Nov 13 20:46:34.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:34.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:34.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:34.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:34.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:34.576: INFO: 
    Nov 13 20:46:36.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:36.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:36.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:36.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
    Nov 13 20:46:36.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:36.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:36.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:36.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:36.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:36.577: INFO: 
    Nov 13 20:46:38.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:38.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:38.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:38.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
    Nov 13 20:46:38.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:38.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:38.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:38.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:38.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:38.575: INFO: 
    Nov 13 20:46:40.582: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:40.582: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:40.582: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:40.582: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
    Nov 13 20:46:40.582: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:40.582: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:40.582: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:40.583: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:40.583: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:40.583: INFO: 
    Nov 13 20:46:42.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:42.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:42.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:42.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
    Nov 13 20:46:42.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:42.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:42.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:42.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:42.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:42.575: INFO: 
    Nov 13 20:46:44.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:44.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:44.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:44.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
    Nov 13 20:46:44.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:44.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:44.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:44.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:44.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:44.574: INFO: 
    Nov 13 20:46:46.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:46.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:46.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:46.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
    Nov 13 20:46:46.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:46.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:46.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:46.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:46.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:46.575: INFO: 
    Nov 13 20:46:48.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:48.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:48.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:48.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
    Nov 13 20:46:48.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:48.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:48.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:48.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:48.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:48.577: INFO: 
    Nov 13 20:46:50.584: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:50.584: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:50.584: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:50.584: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
    Nov 13 20:46:50.584: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:50.584: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:50.584: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:50.584: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:50.584: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:50.584: INFO: 
    Nov 13 20:46:52.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:52.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:52.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:52.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
    Nov 13 20:46:52.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:52.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:52.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:52.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:52.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:52.574: INFO: 
    Nov 13 20:46:54.687: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:54.687: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:54.687: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:54.687: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
    Nov 13 20:46:54.687: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:54.687: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:54.687: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:54.687: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:54.687: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:54.687: INFO: 
    Nov 13 20:46:56.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:56.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:56.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:56.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
    Nov 13 20:46:56.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:56.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:56.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:56.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:56.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:56.574: INFO: 
    Nov 13 20:46:58.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:58.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:58.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:46:58.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
    Nov 13 20:46:58.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:46:58.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:46:58.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:58.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:58.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:46:58.574: INFO: 
    Nov 13 20:47:00.580: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:00.580: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:00.580: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:00.580: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
    Nov 13 20:47:00.580: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:00.580: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:00.580: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:00.580: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:00.580: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:00.580: INFO: 
    Nov 13 20:47:02.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:02.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:02.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:02.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
    Nov 13 20:47:02.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:02.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:02.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:02.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:02.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:02.574: INFO: 
    Nov 13 20:47:04.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:04.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:04.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:04.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
    Nov 13 20:47:04.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:04.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:04.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:04.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:04.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:04.574: INFO: 
    Nov 13 20:47:06.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:06.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:06.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:06.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
    Nov 13 20:47:06.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:06.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:06.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:06.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:06.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:06.577: INFO: 
    Nov 13 20:47:08.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:08.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:08.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:08.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
    Nov 13 20:47:08.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:08.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:08.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:08.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:08.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:08.575: INFO: 
    Nov 13 20:47:10.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:10.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:10.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:10.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
    Nov 13 20:47:10.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:10.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:10.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:10.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:10.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:10.575: INFO: 
    Nov 13 20:47:12.578: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:12.578: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:12.578: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:12.578: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
    Nov 13 20:47:12.578: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:12.578: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:12.578: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:12.578: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:12.578: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:12.578: INFO: 
    Nov 13 20:47:14.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:14.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:14.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:14.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
    Nov 13 20:47:14.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:14.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:14.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:14.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:14.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:14.575: INFO: 
    Nov 13 20:47:16.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:16.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:16.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:16.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
    Nov 13 20:47:16.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:16.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:16.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:16.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:16.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:16.575: INFO: 
    Nov 13 20:47:18.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:18.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:18.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:18.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
    Nov 13 20:47:18.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:18.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:18.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:18.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:18.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:18.574: INFO: 
    Nov 13 20:47:20.579: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:20.579: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:20.579: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:20.579: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
    Nov 13 20:47:20.579: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:20.579: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:20.579: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:20.579: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:20.579: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:20.579: INFO: 
    Nov 13 20:47:22.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:22.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:22.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:22.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
    Nov 13 20:47:22.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:22.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:22.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:22.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:22.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:22.576: INFO: 
    Nov 13 20:47:24.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:24.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:24.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:24.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
    Nov 13 20:47:24.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:24.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:24.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:24.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:24.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:24.575: INFO: 
    Nov 13 20:47:26.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:26.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:26.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:26.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
    Nov 13 20:47:26.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:26.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:26.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:26.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:26.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:26.575: INFO: 
    Nov 13 20:47:28.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:28.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:28.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:28.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
    Nov 13 20:47:28.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:28.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:28.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:28.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:28.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:28.574: INFO: 
    Nov 13 20:47:30.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:30.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:30.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:30.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
    Nov 13 20:47:30.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:30.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:30.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:30.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:30.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:30.576: INFO: 
    Nov 13 20:47:32.579: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:32.579: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:32.579: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:32.579: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
    Nov 13 20:47:32.579: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:32.579: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:32.579: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:32.579: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:32.579: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:32.579: INFO: 
    Nov 13 20:47:34.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:34.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:34.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:34.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
    Nov 13 20:47:34.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:34.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:34.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:34.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:34.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:34.575: INFO: 
    Nov 13 20:47:36.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:36.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:36.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:36.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
    Nov 13 20:47:36.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:36.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:36.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:36.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:36.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:36.577: INFO: 
    Nov 13 20:47:38.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:38.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:38.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:38.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
    Nov 13 20:47:38.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:38.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:38.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:38.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:38.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:38.575: INFO: 
    Nov 13 20:47:40.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:40.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:40.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:40.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
    Nov 13 20:47:40.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:40.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:40.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:40.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:40.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:40.574: INFO: 
    Nov 13 20:47:42.583: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:42.583: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:42.583: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:42.583: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
    Nov 13 20:47:42.583: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:42.583: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:42.583: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:42.583: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:42.583: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:42.583: INFO: 
    Nov 13 20:47:44.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:44.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:44.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:44.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
    Nov 13 20:47:44.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:44.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:44.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:44.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:44.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:44.576: INFO: 
    Nov 13 20:47:46.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:46.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:46.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:46.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
    Nov 13 20:47:46.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:46.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:46.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:46.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:46.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:46.575: INFO: 
    Nov 13 20:47:48.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:48.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:48.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:48.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
    Nov 13 20:47:48.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:48.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:48.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:48.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:48.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:48.574: INFO: 
    Nov 13 20:47:50.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:50.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:50.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:50.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
    Nov 13 20:47:50.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:50.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:50.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:50.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:50.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:50.574: INFO: 
    Nov 13 20:47:52.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:52.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:52.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:52.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
    Nov 13 20:47:52.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:52.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:52.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:52.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:52.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:52.576: INFO: 
    Nov 13 20:47:54.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:54.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:54.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:54.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
    Nov 13 20:47:54.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:54.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:54.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:54.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:54.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:54.574: INFO: 
    Nov 13 20:47:56.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:56.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:56.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:56.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
    Nov 13 20:47:56.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:56.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:56.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:56.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:56.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:56.575: INFO: 
    Nov 13 20:47:58.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:58.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:58.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:47:58.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
    Nov 13 20:47:58.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:47:58.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:47:58.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:58.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:58.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:47:58.576: INFO: 
    Nov 13 20:48:00.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:00.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:00.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:00.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
    Nov 13 20:48:00.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:00.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:00.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:00.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:00.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:00.575: INFO: 
    Nov 13 20:48:02.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:02.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:02.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:02.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
    Nov 13 20:48:02.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:02.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:02.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:02.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:02.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:02.574: INFO: 
    Nov 13 20:48:04.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:04.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:04.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:04.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
    Nov 13 20:48:04.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:04.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:04.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:04.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:04.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:04.576: INFO: 
    Nov 13 20:48:06.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:06.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:06.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:06.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
    Nov 13 20:48:06.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:06.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:06.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:06.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:06.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:06.575: INFO: 
    Nov 13 20:48:08.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:08.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:08.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:08.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
    Nov 13 20:48:08.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:08.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:08.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:08.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:08.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:08.574: INFO: 
    Nov 13 20:48:10.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:10.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:10.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:10.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
    Nov 13 20:48:10.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:10.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:10.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:10.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:10.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:10.575: INFO: 
    Nov 13 20:48:12.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:12.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:12.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:12.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
    Nov 13 20:48:12.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:12.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:12.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:12.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:12.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:12.575: INFO: 
    Nov 13 20:48:14.689: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:14.689: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:14.689: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:14.689: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
    Nov 13 20:48:14.689: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:14.689: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:14.689: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:14.689: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:14.689: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:14.689: INFO: 
    Nov 13 20:48:16.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:16.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:16.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:16.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
    Nov 13 20:48:16.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:16.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:16.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:16.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:16.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:16.575: INFO: 
    Nov 13 20:48:18.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:18.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:18.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:18.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
    Nov 13 20:48:18.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:18.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:18.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:18.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:18.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:18.575: INFO: 
    Nov 13 20:48:20.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:20.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:20.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:20.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
    Nov 13 20:48:20.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:20.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:20.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:20.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:20.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:20.577: INFO: 
    Nov 13 20:48:22.581: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:22.581: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:22.581: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:22.581: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
    Nov 13 20:48:22.581: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:22.581: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:22.581: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:22.581: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:22.581: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:22.581: INFO: 
    Nov 13 20:48:24.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:24.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:24.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:24.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
    Nov 13 20:48:24.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:24.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:24.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:24.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:24.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:24.575: INFO: 
    Nov 13 20:48:26.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:26.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:26.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:26.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
    Nov 13 20:48:26.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:26.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:26.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:26.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:26.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:26.574: INFO: 
    Nov 13 20:48:28.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:28.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:28.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:28.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
    Nov 13 20:48:28.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:28.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:28.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:28.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:28.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:28.574: INFO: 
    Nov 13 20:48:30.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:30.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:30.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:30.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
    Nov 13 20:48:30.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:30.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:30.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:30.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:30.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:30.574: INFO: 
    Nov 13 20:48:32.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:32.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:32.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:32.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
    Nov 13 20:48:32.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:32.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:32.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:32.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:32.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:32.574: INFO: 
    Nov 13 20:48:34.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:34.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:34.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:34.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
    Nov 13 20:48:34.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:34.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:34.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:34.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:34.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:34.577: INFO: 
    Nov 13 20:48:36.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:36.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:36.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:36.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
    Nov 13 20:48:36.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:36.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:36.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:36.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:36.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:36.575: INFO: 
    Nov 13 20:48:38.580: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:38.580: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:38.580: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:38.580: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
    Nov 13 20:48:38.580: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:38.580: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:38.580: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:38.580: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:38.580: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:38.580: INFO: 
    Nov 13 20:48:40.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:40.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:40.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:40.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
    Nov 13 20:48:40.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:40.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:40.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:40.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:40.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:40.576: INFO: 
    Nov 13 20:48:42.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:42.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:42.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:42.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
    Nov 13 20:48:42.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:42.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:42.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:42.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:42.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:42.575: INFO: 
    Nov 13 20:48:44.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:44.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:44.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:44.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
    Nov 13 20:48:44.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:44.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:44.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:44.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:44.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:44.575: INFO: 
    Nov 13 20:48:46.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:46.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:46.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:46.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
    Nov 13 20:48:46.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:46.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:46.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:46.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:46.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:46.574: INFO: 
    Nov 13 20:48:48.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:48.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:48.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:48.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
    Nov 13 20:48:48.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:48.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:48.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:48.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:48.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:48.577: INFO: 
    Nov 13 20:48:50.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:50.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:50.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:50.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
    Nov 13 20:48:50.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:50.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:50.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:50.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:50.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:50.575: INFO: 
    Nov 13 20:48:52.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:52.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:52.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:52.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
    Nov 13 20:48:52.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:52.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:52.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:52.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:52.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:52.575: INFO: 
    Nov 13 20:48:54.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:54.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:54.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:54.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
    Nov 13 20:48:54.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:54.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:54.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:54.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:54.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:54.574: INFO: 
    Nov 13 20:48:56.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:56.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:56.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:56.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
    Nov 13 20:48:56.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:56.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:56.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:56.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:56.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:56.575: INFO: 
    Nov 13 20:48:58.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:58.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:58.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:48:58.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
    Nov 13 20:48:58.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:48:58.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:48:58.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:58.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:58.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:48:58.576: INFO: 
    Nov 13 20:49:00.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:00.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:00.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:00.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
    Nov 13 20:49:00.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:00.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:00.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:00.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:00.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:00.577: INFO: 
    Nov 13 20:49:02.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:02.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:02.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:02.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
    Nov 13 20:49:02.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:02.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:02.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:02.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:02.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:02.575: INFO: 
    Nov 13 20:49:04.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:04.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:04.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:04.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
    Nov 13 20:49:04.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:04.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:04.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:04.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:04.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:04.575: INFO: 
    Nov 13 20:49:06.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:06.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:06.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:06.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
    Nov 13 20:49:06.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:06.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:06.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:06.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:06.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:06.574: INFO: 
    Nov 13 20:49:08.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:08.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:08.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:08.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
    Nov 13 20:49:08.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:08.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:08.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:08.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:08.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:08.575: INFO: 
    Nov 13 20:49:10.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:10.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:10.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:10.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (538 seconds elapsed)
    Nov 13 20:49:10.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:10.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:10.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:10.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:10.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:10.576: INFO: 
    Nov 13 20:49:12.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:12.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:12.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:12.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
    Nov 13 20:49:12.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:12.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:12.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:12.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:12.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:12.576: INFO: 
    Nov 13 20:49:14.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:14.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:14.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:14.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
    Nov 13 20:49:14.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:14.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:14.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:14.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:14.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:14.576: INFO: 
    Nov 13 20:49:16.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:16.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:16.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:16.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
    Nov 13 20:49:16.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:16.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:16.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:16.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:16.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:16.574: INFO: 
    Nov 13 20:49:18.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:18.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:18.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:18.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
    Nov 13 20:49:18.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:18.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:18.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:18.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:18.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:18.575: INFO: 
    Nov 13 20:49:20.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:20.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:20.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:20.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
    Nov 13 20:49:20.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:20.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:20.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:20.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:20.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:20.576: INFO: 
    Nov 13 20:49:22.573: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:22.573: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:22.573: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:22.573: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
    Nov 13 20:49:22.573: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:22.573: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:22.573: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:22.573: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:22.573: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:22.573: INFO: 
    Nov 13 20:49:24.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:24.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:24.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:24.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
    Nov 13 20:49:24.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:24.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:24.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:24.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:24.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:24.575: INFO: 
    Nov 13 20:49:26.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:26.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:26.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:26.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
    Nov 13 20:49:26.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:26.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:26.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:26.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:26.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:26.577: INFO: 
    Nov 13 20:49:28.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:28.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:28.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:28.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
    Nov 13 20:49:28.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:28.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:28.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:28.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:28.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:28.577: INFO: 
    Nov 13 20:49:30.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:30.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:30.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:30.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
    Nov 13 20:49:30.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:30.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:30.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:30.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:30.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:30.576: INFO: 
    Nov 13 20:49:32.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:32.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:32.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:32.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
    Nov 13 20:49:32.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:32.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:32.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:32.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:32.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:32.575: INFO: 
    Nov 13 20:49:34.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:34.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:34.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:34.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
    Nov 13 20:49:34.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:34.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:34.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:34.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:34.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:34.574: INFO: 
    Nov 13 20:49:36.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:36.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:36.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:36.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
    Nov 13 20:49:36.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:36.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:36.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:36.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:36.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:36.575: INFO: 
    Nov 13 20:49:38.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:38.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:38.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:38.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
    Nov 13 20:49:38.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:38.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:38.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:38.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:38.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:38.576: INFO: 
    Nov 13 20:49:40.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:40.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:40.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:40.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
    Nov 13 20:49:40.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:40.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:40.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:40.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:40.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:40.577: INFO: 
    Nov 13 20:49:42.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:42.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:42.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:42.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
    Nov 13 20:49:42.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:42.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:42.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:42.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:42.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:42.575: INFO: 
    Nov 13 20:49:44.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:44.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:44.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:44.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
    Nov 13 20:49:44.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:44.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:44.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:44.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:44.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:44.574: INFO: 
    Nov 13 20:49:46.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:46.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:46.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:46.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
    Nov 13 20:49:46.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:46.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:46.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:46.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:46.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:46.575: INFO: 
    Nov 13 20:49:48.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:48.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:48.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:48.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
    Nov 13 20:49:48.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:48.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:48.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:48.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:48.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:48.575: INFO: 
    Nov 13 20:49:50.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:50.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:50.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:50.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
    Nov 13 20:49:50.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:50.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:50.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:50.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:50.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:50.576: INFO: 
    Nov 13 20:49:52.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:52.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:52.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:52.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
    Nov 13 20:49:52.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:52.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:52.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:52.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:52.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:52.576: INFO: 
    Nov 13 20:49:54.577: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:54.577: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:54.577: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:54.577: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
    Nov 13 20:49:54.577: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:54.577: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:54.577: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:54.577: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:54.577: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:54.577: INFO: 
    Nov 13 20:49:56.576: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:56.576: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:56.576: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:56.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
    Nov 13 20:49:56.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:56.576: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:56.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:56.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:56.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:56.576: INFO: 
    Nov 13 20:49:58.574: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:58.574: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:58.574: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:49:58.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
    Nov 13 20:49:58.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:49:58.574: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:49:58.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:58.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:58.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:49:58.574: INFO: 
    Nov 13 20:50:00.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:50:00.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:50:00.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:50:00.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
    Nov 13 20:50:00.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:50:00.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:50:00.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:50:00.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:50:00.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:50:00.575: INFO: 
    Nov 13 20:50:02.575: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:50:02.575: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:50:02.575: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:50:02.575: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
    Nov 13 20:50:02.575: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:50:02.575: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:50:02.575: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:50:02.575: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:50:02.575: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:50:02.575: INFO: 
    Nov 13 20:50:04.573: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:50:04.573: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:50:04.573: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:50:04.573: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
    Nov 13 20:50:04.573: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
    Nov 13 20:50:04.573: INFO: POD                                                           NODE                                  PHASE    GRACE  CONDITIONS
    Nov 13 20:50:04.573: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:50:04.573: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l  capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:50:04.573: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l           capz-conf-m00n9c-control-plane-jvr6l  Pending         []
    Nov 13 20:50:04.573: INFO: 
    Nov 13 20:50:06.582: INFO: The status of Pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:50:06.582: INFO: The status of Pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:50:06.582: INFO: The status of Pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed

    Nov 13 20:50:06.582: INFO: 15 / 18 pods in namespace 'kube-system' are runnin