PR #112923 pull-kubernetes-e2e-capz-windows-containerd #1591882204663779328
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | pohly: e2e: ginkgo timeouts: use context provided by ginkgo |
| Result | FAILURE |
| Tests | 1 failed / 0 succeeded |
| Started | |
| Elapsed | 1h4m |
| Revision | c40350cb7ecf884112940b235205ba723bef32ee |
| Refs |
112923 |
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
[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
�[1mSTEP�[0m: 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
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
INFO: clusterctl config cluster capz-conf-m00n9c --infrastructure (default) --kubernetes-version v1.26.0-beta.0.65+8e48df13531802 --control-plane-machine-count 1 --worker-machine-count 0 --flavor conformance-presubmit-artifacts-windows-containerd
INFO: Applying the cluster template yaml to the cluster
INFO: Waiting for the cluster infrastructure to be provisioned
�[1mSTEP�[0m: Waiting for cluster to enter the provisioned phase
INFO: Waiting for control plane to be initialized
INFO: Waiting for the first control plane machine managed by capz-conf-m00n9c/capz-conf-m00n9c-control-plane to be provisioned
�[1mSTEP�[0m: Waiting for one control plane node to exist
INFO: Waiting for control plane to be ready
INFO: Waiting for control plane capz-conf-m00n9c/capz-conf-m00n9c-control-plane to be ready (implies underlying nodes to be ready as well)
�[1mSTEP�[0m: Waiting for the control plane to be ready
�[1mSTEP�[0m: Checking all the the control plane machines are in the expected failure domains
INFO: Waiting for the machine deployments to be provisioned
�[1mSTEP�[0m: Waiting for the workload nodes to exist
�[1mSTEP�[0m: Checking all the machines controlled by capz-conf-m00n9c-md-0 are in the "<None>" failure domain
�[1mSTEP�[0m: Waiting for the workload nodes to exist
�[1mSTEP�[0m: Checking all the machines controlled by capz-conf-m00n9c-md-win are in the "<None>" failure domain
INFO: Waiting for the machine pools to be provisioned
INFO: Using repo-list '' for version 'v1.26.0-beta.0.65+8e48df13531802'
�[1mSTEP�[0m: Running e2e test: dir=/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e, command=["-nodes=4" "-slowSpecThreshold=120" "/usr/local/bin/e2e.test" "--" "--e2e-output-dir=/output/e2e-output" "--dump-logs-on-failure=false" "--report-prefix=kubetest." "--num-nodes=2" "--kubeconfig=/tmp/kubeconfig" "--provider=skeleton" "--report-dir=/output" "-ginkgo.slow-spec-threshold=120s" "-ginkgo.timeout=3h" "-ginkgo.trace=true" "-ginkgo.v=true" "-prepull-images=true" "-dump-logs-on-failure=true" "-ginkgo.flakeAttempts=0" "-ginkgo.progress=true" "-ginkgo.skip=\\[LinuxOnly\\]|\\[Serial\\]|\\[Slow\\]|\\[Excluded:WindowsDocker\\]|Networking.Granular.Checks(.*)node-pod.communication|Guestbook.application.should.create.and.stop.a.working.application|device.plugin.for.Windows|Container.Lifecycle.Hook.when.create.a.pod.with.lifecycle.hook.should.execute(.*)http.hook.properly|\\[sig-api-machinery\\].Garbage.collector" "-node-os-distro=windows" "-disable-log-dump=true" "-ginkgo.focus=\\[Conformance\\]|\\[NodeConformance\\]|\\[sig-windows\\]|\\[sig-apps\\].CronJob|\\[sig-api-machinery\\].ResourceQuota|\\[sig-scheduling\\].SchedulerPreemption"]
Running Suite: Kubernetes e2e suite - /usr/local/bin
====================================================
Random Seed: �[1m1668372011�[0m - will randomize all specs
Will run �[1m339�[0m of �[1m7066�[0m specs
Running in parallel across �[1m4�[0m processes
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [606.197 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;243mBegin Captured GinkgoWriter Output >>�[0m
[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 running and ready (594 seconds elapsed)
Nov 13 20:50:06.582: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 13 20:50:06.582: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 13 20:50:06.582: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:06.582: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:06.582: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:06.582: INFO:
Nov 13 20:50: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:50: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:50: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:50:08.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Nov 13 20:50:08.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 13 20:50:08.576: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 13 20:50:08.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:08.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:08.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:08.576: INFO:
Nov 13 20:50: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:50: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:50: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:50:10.576: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Nov 13 20:50:10.576: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 13 20:50:10.576: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 13 20:50:10.576: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:10.576: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:10.576: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:10.576: INFO:
Nov 13 20:50: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:50: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:50: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:50:12.574: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 13 20:50:12.574: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 13 20:50:12.574: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 13 20:50:12.574: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:12.574: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:12.574: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:12.574: INFO:
Nov 13 20:50:12.699: INFO: The status of Pod kube-apiserver-capz-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:12.699: INFO: The status of Pod kube-controller-manager-capz-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:12.699: INFO: The status of Pod kube-scheduler-capz-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:12.699: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 13 20:50:12.699: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 13 20:50:12.699: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 13 20:50:12.699: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:12.699: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:12.699: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:12.699: INFO:
�[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m11/13/22 20:50:12.699�[0m
�[1mSTEP:�[0m Found 124 events. �[38;5;243m11/13/22 20:50:12.749�[0m
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:38 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-m00n9c-control-plane-jvr6l_c769a9ff-9643-4b8f-a9b9-d8ac3233072b became leader
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:38 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-m00n9c-control-plane-jvr6l_ae1ab82f-0cd4-4a78-a20c-ba22daed4230 became leader
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:43 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-787d4945fb to 2
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:44 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-wf2vr
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:44 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-gk4nd
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:44 +0000 UTC - event for coredns-787d4945fb-gk4nd: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:44 +0000 UTC - event for coredns-787d4945fb-wf2vr: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:44 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-lxvnh
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:44 +0000 UTC - event for kube-proxy-lxvnh: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.76_b8873e9b5f48d9"
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:44 +0000 UTC - event for kube-proxy-lxvnh: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-lxvnh to capz-conf-m00n9c-control-plane-jvr6l
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:46 +0000 UTC - event for kube-proxy-lxvnh: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Created: Created container kube-proxy
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:46 +0000 UTC - event for kube-proxy-lxvnh: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Started: Started container kube-proxy
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:46 +0000 UTC - event for kube-proxy-lxvnh: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.76_b8873e9b5f48d9" in 2.108244589s (2.108250289s including waiting)
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:54 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:54 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-scgh2
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:54 +0000 UTC - event for metrics-server-c9574f845-scgh2: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:56 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:56 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-8ptqc
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:56 +0000 UTC - event for calico-kube-controllers-657b584867-8ptqc: {default-scheduler } FailedScheduling: 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:56 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-zrz64
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:56 +0000 UTC - event for calico-node-zrz64: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-zrz64 to capz-conf-m00n9c-control-plane-jvr6l
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:34:56 +0000 UTC - event for calico-node-zrz64: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:04 +0000 UTC - event for calico-node-zrz64: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Started: Started container upgrade-ipam
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:04 +0000 UTC - event for calico-node-zrz64: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Created: Created container upgrade-ipam
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:04 +0000 UTC - event for calico-node-zrz64: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 7.724447549s (7.724470549s including waiting)
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:08 +0000 UTC - event for calico-node-zrz64: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:08 +0000 UTC - event for calico-node-zrz64: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Created: Created container install-cni
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:08 +0000 UTC - event for calico-node-zrz64: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Started: Started container install-cni
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:10 +0000 UTC - event for calico-kube-controllers-657b584867-8ptqc: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-8ptqc to capz-conf-m00n9c-control-plane-jvr6l
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:10 +0000 UTC - event for coredns-787d4945fb-gk4nd: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-gk4nd to capz-conf-m00n9c-control-plane-jvr6l
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:10 +0000 UTC - event for coredns-787d4945fb-wf2vr: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-wf2vr to capz-conf-m00n9c-control-plane-jvr6l
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:10 +0000 UTC - event for metrics-server-c9574f845-scgh2: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-scgh2 to capz-conf-m00n9c-control-plane-jvr6l
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:11 +0000 UTC - event for calico-kube-controllers-657b584867-8ptqc: {kubelet capz-conf-m00n9c-control-plane-jvr6l} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "0726886b4735d3fb5837c1d701f330c9b6cebb98c5bfa4f805a49ac81679b944": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:11 +0000 UTC - event for calico-node-zrz64: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:11 +0000 UTC - event for coredns-787d4945fb-gk4nd: {kubelet capz-conf-m00n9c-control-plane-jvr6l} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "9090a070178286d50b035ae4957be252ee2bdde48203ba76e76952eab14bbf0e": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:11 +0000 UTC - event for coredns-787d4945fb-wf2vr: {kubelet capz-conf-m00n9c-control-plane-jvr6l} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "21a12746c379e3dde47eb174bb2ec6eedf050aa064b7d0e4df2912e8e5694a0a": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:11 +0000 UTC - event for metrics-server-c9574f845-scgh2: {kubelet capz-conf-m00n9c-control-plane-jvr6l} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "598ba56b269a039b3d5ca25240c96e8afa30669379c3dde242cc9317d511e68b": plugin type="calico" failed (add): stat /var/lib/calico/nodename: no such file or directory: check that the calico/node container is running and has mounted /var/lib/calico/
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:18 +0000 UTC - event for calico-node-zrz64: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 7.452077206s (7.452131407s including waiting)
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:18 +0000 UTC - event for calico-node-zrz64: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Started: Started container calico-node
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:18 +0000 UTC - event for calico-node-zrz64: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Created: Created container calico-node
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:19 +0000 UTC - event for calico-node-zrz64: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Unhealthy: Readiness probe failed: calico/node is not ready: felix is not ready: Get "http://localhost:9099/readiness": dial tcp [::1]:9099: connect: connection refused
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:22 +0000 UTC - event for calico-kube-controllers-657b584867-8ptqc: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0"
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:25 +0000 UTC - event for coredns-787d4945fb-wf2vr: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:25 +0000 UTC - event for coredns-787d4945fb-wf2vr: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Created: Created container coredns
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:26 +0000 UTC - event for coredns-787d4945fb-wf2vr: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Started: Started container coredns
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:26 +0000 UTC - event for coredns-787d4945fb-wf2vr: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Unhealthy: Readiness probe failed: Get "http://192.168.218.2:8181/ready": dial tcp 192.168.218.2:8181: connect: connection refused
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:26 +0000 UTC - event for metrics-server-c9574f845-scgh2: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:27 +0000 UTC - event for coredns-787d4945fb-gk4nd: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:27 +0000 UTC - event for coredns-787d4945fb-gk4nd: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Started: Started container coredns
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:27 +0000 UTC - event for coredns-787d4945fb-gk4nd: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Created: Created container coredns
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:28 +0000 UTC - event for calico-kube-controllers-657b584867-8ptqc: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 6.15157014s (6.151647638s including waiting)
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:28 +0000 UTC - event for calico-kube-controllers-657b584867-8ptqc: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Created: Created container calico-kube-controllers
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:28 +0000 UTC - event for calico-kube-controllers-657b584867-8ptqc: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Started: Started container calico-kube-controllers
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:28 +0000 UTC - event for coredns-787d4945fb-gk4nd: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Unhealthy: Readiness probe failed: Get "http://192.168.218.4:8181/ready": dial tcp 192.168.218.4:8181: connect: connection refused
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:32 +0000 UTC - event for metrics-server-c9574f845-scgh2: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Started: Started container metrics-server
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:32 +0000 UTC - event for metrics-server-c9574f845-scgh2: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Created: Created container metrics-server
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:35:32 +0000 UTC - event for metrics-server-c9574f845-scgh2: {kubelet capz-conf-m00n9c-control-plane-jvr6l} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 4.166364543s (5.999197999s including waiting)
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:26 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-qq48l
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:26 +0000 UTC - event for calico-node-windows-qq48l: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-qq48l to capz-conf-4qhqp
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:26 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-ct6l5
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:26 +0000 UTC - event for containerd-logger-ct6l5: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-ct6l5 to capz-conf-4qhqp
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:26 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-ql74d
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:26 +0000 UTC - event for kube-proxy-windows-ql74d: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-ql74d to capz-conf-4qhqp
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:28 +0000 UTC - event for containerd-logger-ct6l5: {kubelet capz-conf-4qhqp} FailedMount: MountVolume.SetUp failed for volume "containerd-logger-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:28 +0000 UTC - event for kube-proxy-windows-ql74d: {kubelet capz-conf-4qhqp} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:46 +0000 UTC - event for calico-node-windows-qq48l: {kubelet capz-conf-4qhqp} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:46 +0000 UTC - event for containerd-logger-ct6l5: {kubelet capz-conf-4qhqp} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:46 +0000 UTC - event for kube-proxy-windows-ql74d: {kubelet capz-conf-4qhqp} Created: Created container kube-proxy
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:46 +0000 UTC - event for kube-proxy-windows-ql74d: {kubelet capz-conf-4qhqp} Pulled: Container image "sigwindowstools/kube-proxy:v1.26.0-beta.0.65_8e48df13531802-calico-hostprocess" already present on machine
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:47 +0000 UTC - event for kube-proxy-windows-ql74d: {kubelet capz-conf-4qhqp} Started: Started container kube-proxy
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:50 +0000 UTC - event for containerd-logger-ct6l5: {kubelet capz-conf-4qhqp} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 3.754408s (3.754408s including waiting)
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:56 +0000 UTC - event for calico-node-windows-qq48l: {kubelet capz-conf-4qhqp} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 5.966747s (9.6605487s including waiting)
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:56 +0000 UTC - event for calico-node-windows-qq48l: {kubelet capz-conf-4qhqp} Started: Started container install-cni
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:56 +0000 UTC - event for calico-node-windows-qq48l: {kubelet capz-conf-4qhqp} Created: Created container install-cni
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:58 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-fk96m
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:58 +0000 UTC - event for csi-proxy-fk96m: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-fk96m to capz-conf-4qhqp
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:59 +0000 UTC - event for containerd-logger-ct6l5: {kubelet capz-conf-4qhqp} Created: Created container containerd-logger
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:59 +0000 UTC - event for containerd-logger-ct6l5: {kubelet capz-conf-4qhqp} Started: Started container containerd-logger
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:37:59 +0000 UTC - event for csi-proxy-fk96m: {kubelet capz-conf-4qhqp} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:02 +0000 UTC - event for calico-node-windows-qq48l: {kubelet capz-conf-4qhqp} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:16 +0000 UTC - event for csi-proxy-fk96m: {kubelet capz-conf-4qhqp} Created: Created container csi-proxy
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:16 +0000 UTC - event for csi-proxy-fk96m: {kubelet capz-conf-4qhqp} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 16.990575s (16.9911042s including waiting)
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:16 +0000 UTC - event for csi-proxy-fk96m: {kubelet capz-conf-4qhqp} Started: Started container csi-proxy
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:21 +0000 UTC - event for calico-node-windows-qq48l: {kubelet capz-conf-4qhqp} Started: Started container calico-node-startup
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:21 +0000 UTC - event for calico-node-windows-qq48l: {kubelet capz-conf-4qhqp} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 436.3573ms (436.3573ms including waiting)
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:21 +0000 UTC - event for calico-node-windows-qq48l: {kubelet capz-conf-4qhqp} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:21 +0000 UTC - event for calico-node-windows-qq48l: {kubelet capz-conf-4qhqp} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 4.6929369s (18.7829543s including waiting)
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:21 +0000 UTC - event for calico-node-windows-qq48l: {kubelet capz-conf-4qhqp} Created: Created container calico-node-startup
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:29 +0000 UTC - event for calico-node-windows-qq48l: {kubelet capz-conf-4qhqp} Created: Created container calico-node-felix
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:29 +0000 UTC - event for calico-node-windows-qq48l: {kubelet capz-conf-4qhqp} Started: Started container calico-node-felix
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:38 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-k2x9h
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:38 +0000 UTC - event for calico-node-windows-k2x9h: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-k2x9h to capz-conf-fs5d4
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:38 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-cbjfp
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:38 +0000 UTC - event for containerd-logger-cbjfp: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-cbjfp to capz-conf-fs5d4
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:38 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-ldf97
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:38 +0000 UTC - event for kube-proxy-windows-ldf97: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-ldf97 to capz-conf-fs5d4
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:40 +0000 UTC - event for calico-node-windows-k2x9h: {kubelet capz-conf-fs5d4} FailedMount: MountVolume.SetUp failed for volume "calico-static-rules" : failed to sync configmap cache: timed out waiting for the condition
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:52 +0000 UTC - event for calico-node-windows-qq48l: {kubelet capz-conf-4qhqp} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 387.2434ms (387.2434ms including waiting)
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:59 +0000 UTC - event for calico-node-windows-k2x9h: {kubelet capz-conf-fs5d4} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:59 +0000 UTC - event for containerd-logger-cbjfp: {kubelet capz-conf-fs5d4} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:59 +0000 UTC - event for kube-proxy-windows-ldf97: {kubelet capz-conf-fs5d4} Created: Created container kube-proxy
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:38:59 +0000 UTC - event for kube-proxy-windows-ldf97: {kubelet capz-conf-fs5d4} Pulled: Container image "sigwindowstools/kube-proxy:v1.26.0-beta.0.65_8e48df13531802-calico-hostprocess" already present on machine
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:00 +0000 UTC - event for kube-proxy-windows-ldf97: {kubelet capz-conf-fs5d4} Started: Started container kube-proxy
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:04 +0000 UTC - event for calico-node-windows-k2x9h: {kubelet capz-conf-fs5d4} Started: Started container install-cni
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:04 +0000 UTC - event for calico-node-windows-k2x9h: {kubelet capz-conf-fs5d4} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 4.4311074s (4.4311074s including waiting)
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:04 +0000 UTC - event for calico-node-windows-k2x9h: {kubelet capz-conf-fs5d4} Created: Created container install-cni
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:07 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-dz98b
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:07 +0000 UTC - event for csi-proxy-dz98b: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-dz98b to capz-conf-fs5d4
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:08 +0000 UTC - event for containerd-logger-cbjfp: {kubelet capz-conf-fs5d4} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 3.910245s (8.3205627s including waiting)
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:08 +0000 UTC - event for csi-proxy-dz98b: {kubelet capz-conf-fs5d4} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:09 +0000 UTC - event for calico-node-windows-k2x9h: {kubelet capz-conf-fs5d4} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:16 +0000 UTC - event for containerd-logger-cbjfp: {kubelet capz-conf-fs5d4} Created: Created container containerd-logger
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:17 +0000 UTC - event for containerd-logger-cbjfp: {kubelet capz-conf-fs5d4} Started: Started container containerd-logger
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:28 +0000 UTC - event for csi-proxy-dz98b: {kubelet capz-conf-fs5d4} Started: Started container csi-proxy
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:28 +0000 UTC - event for csi-proxy-dz98b: {kubelet capz-conf-fs5d4} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 20.1766127s (20.1766127s including waiting)
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:28 +0000 UTC - event for csi-proxy-dz98b: {kubelet capz-conf-fs5d4} Created: Created container csi-proxy
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:32 +0000 UTC - event for calico-node-windows-k2x9h: {kubelet capz-conf-fs5d4} Created: Created container calico-node-startup
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:32 +0000 UTC - event for calico-node-windows-k2x9h: {kubelet capz-conf-fs5d4} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 4.4276984s (23.3439631s including waiting)
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:33 +0000 UTC - event for calico-node-windows-k2x9h: {kubelet capz-conf-fs5d4} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 408.8619ms (408.8619ms including waiting)
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:33 +0000 UTC - event for calico-node-windows-k2x9h: {kubelet capz-conf-fs5d4} Started: Started container calico-node-startup
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:33 +0000 UTC - event for calico-node-windows-k2x9h: {kubelet capz-conf-fs5d4} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:40 +0000 UTC - event for calico-node-windows-k2x9h: {kubelet capz-conf-fs5d4} Created: Created container calico-node-felix
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:39:40 +0000 UTC - event for calico-node-windows-k2x9h: {kubelet capz-conf-fs5d4} Started: Started container calico-node-felix
Nov 13 20:50:12.749: INFO: At 2022-11-13 20:40:08 +0000 UTC - event for calico-node-windows-k2x9h: {kubelet capz-conf-fs5d4} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 394.4278ms (394.4278ms including waiting)
Nov 13 20:50:12.804: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 13 20:50:12.804: INFO: calico-kube-controllers-657b584867-8ptqc capz-conf-m00n9c-control-plane-jvr6l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:10 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:29 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:29 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:10 +0000 UTC }]
Nov 13 20:50:12.804: 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 True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:40:15 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:40:15 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:38:38 +0000 UTC }]
Nov 13 20:50:12.804: INFO: calico-node-windows-qq48l capz-conf-4qhqp Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:38:02 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:38:59 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:38:59 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:37:26 +0000 UTC }]
Nov 13 20:50:12.804: INFO: calico-node-zrz64 capz-conf-m00n9c-control-plane-jvr6l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:11 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:20 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:20 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:34:56 +0000 UTC }]
Nov 13 20:50:12.804: INFO: containerd-logger-cbjfp capz-conf-fs5d4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:38:38 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:39:17 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:39:17 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:38:38 +0000 UTC }]
Nov 13 20:50:12.804: INFO: containerd-logger-ct6l5 capz-conf-4qhqp Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:37:27 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:38:00 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:38:00 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:37:26 +0000 UTC }]
Nov 13 20:50:12.804: INFO: coredns-787d4945fb-gk4nd capz-conf-m00n9c-control-plane-jvr6l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:10 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:31 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:31 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:10 +0000 UTC }]
Nov 13 20:50:12.804: INFO: coredns-787d4945fb-wf2vr capz-conf-m00n9c-control-plane-jvr6l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:10 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:31 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:31 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:10 +0000 UTC }]
Nov 13 20:50:12.804: INFO: csi-proxy-dz98b capz-conf-fs5d4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:39:07 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:39:29 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:39:29 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:39:07 +0000 UTC }]
Nov 13 20:50:12.804: INFO: csi-proxy-fk96m capz-conf-4qhqp Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:37:58 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:38:17 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:38:17 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:37:58 +0000 UTC }]
Nov 13 20:50:12.804: INFO: etcd-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:34:39 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:34:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:34:48 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:34:39 +0000 UTC }]
Nov 13 20:50:12.804: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:12.804: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:12.804: INFO: kube-proxy-lxvnh capz-conf-m00n9c-control-plane-jvr6l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:34:44 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:34:47 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:34:47 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:34:44 +0000 UTC }]
Nov 13 20:50:12.804: INFO: kube-proxy-windows-ldf97 capz-conf-fs5d4 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:38:38 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:39:00 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:39:00 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:38:38 +0000 UTC }]
Nov 13 20:50:12.804: INFO: kube-proxy-windows-ql74d capz-conf-4qhqp Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:37:27 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:37:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:37:48 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:37:26 +0000 UTC }]
Nov 13 20:50:12.804: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Nov 13 20:50:12.804: INFO: metrics-server-c9574f845-scgh2 capz-conf-m00n9c-control-plane-jvr6l Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:10 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:36:01 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:36:01 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-13 20:35:10 +0000 UTC }]
Nov 13 20:50:12.804: INFO:
Nov 13 20:50:13.300: INFO:
Logging node info for node capz-conf-4qhqp
Nov 13 20:50:13.486: INFO: Node Info: &Node{ObjectMeta:{capz-conf-4qhqp 91b014b1-1efb-4f79-8ee9-e5c8fa8c9b0c 2008 0 2022-11-13 20:37:26 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D4s_v3 beta.kubernetes.io/os:windows failure-domain.beta.kubernetes.io/region:canadacentral failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-4qhqp kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-m00n9c cluster.x-k8s.io/cluster-namespace:capz-conf-m00n9c cluster.x-k8s.io/machine:capz-conf-m00n9c-md-win-7d8fd48fdc-qzhzd cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-m00n9c-md-win-7d8fd48fdc kubeadm.alpha.kubernetes.io/cri-socket:npipe:////./pipe/containerd-containerd node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.1.0.4/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.172.1 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:c9:4c:8e volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-13 20:37:26 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-13 20:37:26 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:node.kubernetes.io/windows-build":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2022-11-13 20:37:58 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-13 20:38:26 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {Go-http-client Update v1 2022-11-13 20:38:49 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{},"f:projectcalico.org/VXLANTunnelMACAddr":{}}}} status} {kubelet.exe Update v1 2022-11-13 20:48:41 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-m00n9c/providers/Microsoft.Compute/virtualMachines/capz-conf-4qhqp,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{8 0} {<nil>} 8 DecimalSI},cpu: {{4 0} {<nil>} 4 DecimalSI},ephemeral-storage: {{136912564224 0} {<nil>} 133703676Ki BinarySI},memory: {{17179398144 0} {<nil>} 16776756Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{8 0} {<nil>} 8 DecimalSI},cpu: {{4 0} {<nil>} 4 DecimalSI},ephemeral-storage: {{123221307598 0} {<nil>} 123221307598 DecimalSI},memory: {{17074540544 0} {<nil>} 16674356Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-13 20:48:41 +0000 UTC,LastTransitionTime:2022-11-13 20:37:26 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-13 20:48:41 +0000 UTC,LastTransitionTime:2022-11-13 20:37:26 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-13 20:48:41 +0000 UTC,LastTransitionTime:2022-11-13 20:37:26 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-13 20:48:41 +0000 UTC,LastTransitionTime:2022-11-13 20:37:58 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-4qhqp,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-4qhqp,SystemUUID:DB63F397-50CA-4963-92B5-3D31390157D8,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.26.0-beta.0.76+b8873e9b5f48d9-dirty,KubeProxyVersion:v1.26.0-beta.0.76+b8873e9b5f48d9-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.26.0-beta.0.65_8e48df13531802-calico-hostprocess],SizeBytes:116182072,},ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/csi-proxy@sha256:96b4144986319a747ba599892454be2737aae6005d96b8e13ed481321ac3afba ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2],SizeBytes:109639330,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:104158827,},ContainerImage{Names:[docker.io/sigwindowstools/calico-install@sha256:1dac2d6534d9017f8967cc6238d6b448bdc1c978b5e8fea91bf39dc59d29881f docker.io/sigwindowstools/calico-install:v3.23.0-hostprocess],SizeBytes:47258351,},ContainerImage{Names:[docker.io/sigwindowstools/calico-node@sha256:6ea7a987c109fdc059a36bf4abc5267c6f3de99d02ef6e84f0826da2aa435ea5 docker.io/sigwindowstools/calico-node:v3.23.0-hostprocess],SizeBytes:27005594,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Nov 13 20:50:13.487: INFO:
Logging kubelet events for node capz-conf-4qhqp
Nov 13 20:50:13.683: INFO:
Logging pods the kubelet thinks is on node capz-conf-4qhqp
Nov 13 20:50:13.902: INFO: containerd-logger-ct6l5 started at 2022-11-13 20:37:27 +0000 UTC (0+1 container statuses recorded)
Nov 13 20:50:13.902: INFO: Container containerd-logger ready: true, restart count 0
Nov 13 20:50:13.902: INFO: kube-proxy-windows-ql74d started at 2022-11-13 20:37:27 +0000 UTC (0+1 container statuses recorded)
Nov 13 20:50:13.902: INFO: Container kube-proxy ready: true, restart count 0
Nov 13 20:50:13.902: INFO: calico-node-windows-qq48l started at 2022-11-13 20:37:27 +0000 UTC (1+2 container statuses recorded)
Nov 13 20:50:13.902: INFO: Init container install-cni ready: true, restart count 0
Nov 13 20:50:13.902: INFO: Container calico-node-felix ready: true, restart count 1
Nov 13 20:50:13.902: INFO: Container calico-node-startup ready: true, restart count 0
Nov 13 20:50:13.902: INFO: csi-proxy-fk96m started at 2022-11-13 20:37:58 +0000 UTC (0+1 container statuses recorded)
Nov 13 20:50:13.902: INFO: Container csi-proxy ready: true, restart count 0
Nov 13 20:50:14.556: INFO:
Latency metrics for node capz-conf-4qhqp
Nov 13 20:50:14.556: INFO:
Logging node info for node capz-conf-fs5d4
Nov 13 20:50:14.685: INFO: Node Info: &Node{ObjectMeta:{capz-conf-fs5d4 995b9658-b1f5-4b03-a862-a90dbe56cc15 2117 0 2022-11-13 20:38:38 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D4s_v3 beta.kubernetes.io/os:windows failure-domain.beta.kubernetes.io/region:canadacentral failure-domain.beta.kubernetes.io/zone:0 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-fs5d4 kubernetes.io/os:windows node.kubernetes.io/instance-type:Standard_D4s_v3 node.kubernetes.io/windows-build:10.0.17763 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:0] map[cluster.x-k8s.io/cluster-name:capz-conf-m00n9c cluster.x-k8s.io/cluster-namespace:capz-conf-m00n9c cluster.x-k8s.io/machine:capz-conf-m00n9c-md-win-7d8fd48fdc-7kzww cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-m00n9c-md-win-7d8fd48fdc kubeadm.alpha.kubernetes.io/cri-socket:npipe:////./pipe/containerd-containerd node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.1.0.5/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.125.193 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:7f:17:84 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-13 20:38:38 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-13 20:38:38 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:node.kubernetes.io/windows-build":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kube-controller-manager Update v1 2022-11-13 20:39:07 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-13 20:40:01 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {Go-http-client Update v1 2022-11-13 20:40:05 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{},"f:projectcalico.org/VXLANTunnelMACAddr":{}}}} status} {kubelet.exe Update v1 2022-11-13 20:49:53 +0000 UTC FieldsV1 {"f:status":{"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-m00n9c/providers/Microsoft.Compute/virtualMachines/capz-conf-fs5d4,Unschedulable:false,Taints:[]Taint{},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{8 0} {<nil>} 8 DecimalSI},cpu: {{4 0} {<nil>} 4 DecimalSI},ephemeral-storage: {{136912564224 0} {<nil>} 133703676Ki BinarySI},memory: {{17179398144 0} {<nil>} 16776756Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{8 0} {<nil>} 8 DecimalSI},cpu: {{4 0} {<nil>} 4 DecimalSI},ephemeral-storage: {{123221307598 0} {<nil>} 123221307598 DecimalSI},memory: {{17074540544 0} {<nil>} 16674356Ki BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-13 20:49:53 +0000 UTC,LastTransitionTime:2022-11-13 20:38:38 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-13 20:49:53 +0000 UTC,LastTransitionTime:2022-11-13 20:38:38 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-13 20:49:53 +0000 UTC,LastTransitionTime:2022-11-13 20:38:38 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-13 20:49:53 +0000 UTC,LastTransitionTime:2022-11-13 20:39:07 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-fs5d4,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-fs5d4,SystemUUID:898B109F-1858-41FA-B8E0-CCC3844B52F8,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.26.0-beta.0.76+b8873e9b5f48d9-dirty,KubeProxyVersion:v1.26.0-beta.0.76+b8873e9b5f48d9-dirty,OperatingSystem:windows,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger@sha256:63bf2aa9db909d0d90fb5205abf7fb2a6d9a494b89cbd2508a42457dfc875505 ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0],SizeBytes:133732668,},ContainerImage{Names:[docker.io/sigwindowstools/kube-proxy:v1.23.1-calico-hostprocess docker.io/sigwindowstools/kube-proxy:v1.26.0-beta.0.65_8e48df13531802-calico-hostprocess],SizeBytes:116182072,},ContainerImage{Names:[ghcr.io/kubernetes-sigs/sig-windows/csi-proxy@sha256:96b4144986319a747ba599892454be2737aae6005d96b8e13ed481321ac3afba ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2],SizeBytes:109639330,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:104158827,},ContainerImage{Names:[docker.io/sigwindowstools/calico-install@sha256:1dac2d6534d9017f8967cc6238d6b448bdc1c978b5e8fea91bf39dc59d29881f docker.io/sigwindowstools/calico-install:v3.23.0-hostprocess],SizeBytes:47258351,},ContainerImage{Names:[docker.io/sigwindowstools/calico-node@sha256:6ea7a987c109fdc059a36bf4abc5267c6f3de99d02ef6e84f0826da2aa435ea5 docker.io/sigwindowstools/calico-node:v3.23.0-hostprocess],SizeBytes:27005594,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Nov 13 20:50:14.686: INFO:
Logging kubelet events for node capz-conf-fs5d4
Nov 13 20:50:14.883: INFO:
Logging pods the kubelet thinks is on node capz-conf-fs5d4
Nov 13 20:50:15.100: INFO: kube-proxy-windows-ldf97 started at 2022-11-13 20:38:38 +0000 UTC (0+1 container statuses recorded)
Nov 13 20:50:15.100: INFO: Container kube-proxy ready: true, restart count 0
Nov 13 20:50:15.100: INFO: calico-node-windows-k2x9h started at 2022-11-13 20:38:38 +0000 UTC (1+2 container statuses recorded)
Nov 13 20:50:15.100: INFO: Init container install-cni ready: true, restart count 0
Nov 13 20:50:15.100: INFO: Container calico-node-felix ready: true, restart count 1
Nov 13 20:50:15.100: INFO: Container calico-node-startup ready: true, restart count 0
Nov 13 20:50:15.100: INFO: containerd-logger-cbjfp started at 2022-11-13 20:38:38 +0000 UTC (0+1 container statuses recorded)
Nov 13 20:50:15.100: INFO: Container containerd-logger ready: true, restart count 0
Nov 13 20:50:15.100: INFO: csi-proxy-dz98b started at 2022-11-13 20:39:07 +0000 UTC (0+1 container statuses recorded)
Nov 13 20:50:15.100: INFO: Container csi-proxy ready: true, restart count 0
Nov 13 20:50:15.751: INFO:
Latency metrics for node capz-conf-fs5d4
Nov 13 20:50:15.751: INFO:
Logging node info for node capz-conf-m00n9c-control-plane-jvr6l
Nov 13 20:50:15.887: INFO: Node Info: &Node{ObjectMeta:{capz-conf-m00n9c-control-plane-jvr6l 61bf034d-465d-4b41-9bdf-224b7c982ab4 1755 0 2022-11-13 20:34:35 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:canadacentral failure-domain.beta.kubernetes.io/zone:canadacentral-3 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-m00n9c-control-plane-jvr6l kubernetes.io/os:linux node-role.kubernetes.io/control-plane: node.kubernetes.io/exclude-from-external-load-balancers: node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:canadacentral-3] map[cluster.x-k8s.io/cluster-name:capz-conf-m00n9c cluster.x-k8s.io/cluster-namespace:capz-conf-m00n9c cluster.x-k8s.io/machine:capz-conf-m00n9c-control-plane-cl9d5 cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-m00n9c-control-plane kubeadm.alpha.kubernetes.io/cri-socket:unix:///var/run/containerd/containerd.sock node.alpha.kubernetes.io/ttl:0 projectcalico.org/IPv4Address:10.0.0.4/16 projectcalico.org/IPv4VXLANTunnelAddr:192.168.218.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2022-11-13 20:34:35 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kubeadm Update v1 2022-11-13 20:34:37 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}},"f:labels":{"f:node-role.kubernetes.io/control-plane":{},"f:node.kubernetes.io/exclude-from-external-load-balancers":{}}}} } {manager Update v1 2022-11-13 20:34:53 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:cluster.x-k8s.io/cluster-name":{},"f:cluster.x-k8s.io/cluster-namespace":{},"f:cluster.x-k8s.io/machine":{},"f:cluster.x-k8s.io/owner-kind":{},"f:cluster.x-k8s.io/owner-name":{}}}} } {kube-controller-manager Update v1 2022-11-13 20:35:10 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2022-11-13 20:35:19 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:projectcalico.org/IPv4Address":{},"f:projectcalico.org/IPv4VXLANTunnelAddr":{}}},"f:status":{"f:conditions":{"k:{\"type\":\"NetworkUnavailable\"}":{".":{},"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{},"f:type":{}}}}} status} {kubelet Update v1 2022-11-13 20:45:51 +0000 UTC FieldsV1 {"f:status":{"f:allocatable":{"f:ephemeral-storage":{}},"f:conditions":{"k:{\"type\":\"DiskPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"MemoryPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"PIDPressure\"}":{"f:lastHeartbeatTime":{}},"k:{\"type\":\"Ready\"}":{"f:lastHeartbeatTime":{},"f:lastTransitionTime":{},"f:message":{},"f:reason":{},"f:status":{}}},"f:images":{}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/===REDACTED===/resourceGroups/capz-conf-m00n9c/providers/Microsoft.Compute/virtualMachines/capz-conf-m00n9c-control-plane-jvr6l,Unschedulable:false,Taints:[]Taint{Taint{Key:node-role.kubernetes.io/control-plane,Value:,Effect:NoSchedule,TimeAdded:<nil>,},},ConfigSource:nil,PodCIDRs:[],},Status:NodeStatus{Capacity:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{133003395072 0} {<nil>} BinarySI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8344723456 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Allocatable:ResourceList{attachable-volumes-azure-disk: {{4 0} {<nil>} 4 DecimalSI},cpu: {{2 0} {<nil>} 2 DecimalSI},ephemeral-storage: {{119703055367 0} {<nil>} 119703055367 DecimalSI},hugepages-1Gi: {{0 0} {<nil>} 0 DecimalSI},hugepages-2Mi: {{0 0} {<nil>} 0 DecimalSI},memory: {{8239865856 0} {<nil>} BinarySI},pods: {{110 0} {<nil>} 110 DecimalSI},},Phase:,Conditions:[]NodeCondition{NodeCondition{Type:NetworkUnavailable,Status:False,LastHeartbeatTime:2022-11-13 20:35:18 +0000 UTC,LastTransitionTime:2022-11-13 20:35:18 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-13 20:45:51 +0000 UTC,LastTransitionTime:2022-11-13 20:34:20 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-13 20:45:51 +0000 UTC,LastTransitionTime:2022-11-13 20:34:20 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-13 20:45:51 +0000 UTC,LastTransitionTime:2022-11-13 20:34:20 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-13 20:45:51 +0000 UTC,LastTransitionTime:2022-11-13 20:35:10 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-m00n9c-control-plane-jvr6l,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:7c5e645ce75f4d0daaee6b990820a461,SystemUUID:0f2df4db-2032-ce42-b3de-7f9df7a61030,BootID:16767b0d-a3de-4917-87c2-8933fbf64080,KernelVersion:5.4.0-1091-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.26.0-beta.0.76+b8873e9b5f48d9,KubeProxyVersion:v1.26.0-beta.0.76+b8873e9b5f48d9,OperatingSystem:linux,Architecture:amd64,},Images:[]ContainerImage{ContainerImage{Names:[docker.io/calico/cni@sha256:914823d144204288f881e49b93b6852febfe669074cd4e2a782860981615f521 docker.io/calico/cni:v3.23.0],SizeBytes:110494683,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:b83c1d70989e1fe87583607bf5aee1ee34e52773d4755b95f5cf5a451962f3a4 registry.k8s.io/etcd:3.5.5-0],SizeBytes:102417044,},ContainerImage{Names:[registry.k8s.io/etcd@sha256:6f72b851544986cb0921b53ea655ec04c36131248f16d4ad110cb3ca0c369dc1 registry.k8s.io/etcd:3.5.4-0],SizeBytes:102157811,},ContainerImage{Names:[docker.io/calico/node@sha256:4763820ecb4d8e82483a2ffabfec7fcded9603318692df210a778d223a4d7474 docker.io/calico/node:v3.23.0],SizeBytes:71573794,},ContainerImage{Names:[docker.io/calico/kube-controllers@sha256:78bc199299f966b0694dc4044501aee2d7ebd6862b2b0a00bca3ee8d3813c82f docker.io/calico/kube-controllers:v3.23.0],SizeBytes:56343954,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-apiserver@sha256:ec69d1434d36d220ed8080dce242380284d4166daacb073dbc6d82e11bb1d9c4 gcr.io/k8s-staging-ci-images/kube-apiserver:v1.26.0-beta.0.65_8e48df13531802],SizeBytes:35316538,},ContainerImage{Names:[registry.k8s.io/kube-apiserver@sha256:4188262a351f156e8027ff81693d771c35b34b668cbd61e59c4a4490dd5c08f3 registry.k8s.io/kube-apiserver:v1.25.3],SizeBytes:34238163,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-controller-manager@sha256:bca35bdba72c14884db646f3bbf5334247c840b47a196ba6aad1bd4a8481bef0 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.26.0-beta.0.65_8e48df13531802],SizeBytes:32240596,},ContainerImage{Names:[registry.k8s.io/kube-controller-manager@sha256:d3a06262256f3e7578d5f77df137a8cdf58f9f498f35b5b56d116e8a7e31dc91 registry.k8s.io/kube-controller-manager:v1.25.3],SizeBytes:31261869,},ContainerImage{Names:[k8s.gcr.io/metrics-server/metrics-server@sha256:6385aec64bb97040a5e692947107b81e178555c7a5b71caa90d733e4130efc10 k8s.gcr.io/metrics-server/metrics-server:v0.5.2],SizeBytes:26023008,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:fbd439680dd72c3e4facc929a7a135d11fbf949e2099357d50b28132d086ccd9 gcr.io/k8s-staging-ci-images/kube-proxy:v1.26.0-beta.0.65_8e48df13531802],SizeBytes:21534778,},ContainerImage{Names:[capzci.azurecr.io/kube-proxy@sha256:925eb4c86d6dfc28d88ac41a1fc49517d0748e7b5507299c3083c251bdad6957 capzci.azurecr.io/kube-proxy:v1.26.0-beta.0.76_b8873e9b5f48d9],SizeBytes:21532929,},ContainerImage{Names:[registry.k8s.io/kube-proxy@sha256:6bf25f038543e1f433cb7f2bdda445ed348c7b9279935ebc2ae4f432308ed82f registry.k8s.io/kube-proxy:v1.25.3],SizeBytes:20265805,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-scheduler@sha256:ba0a3921d93c8461119feb344fd9341c2e128206857da6ad515d5da42378e9b1 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.26.0-beta.0.65_8e48df13531802],SizeBytes:17482660,},ContainerImage{Names:[registry.k8s.io/kube-scheduler@sha256:f478aa916568b00269068ff1e9ff742ecc16192eb6e371e30f69f75df904162e registry.k8s.io/kube-scheduler:v1.25.3],SizeBytes:15798744,},ContainerImage{Names:[registry.k8s.io/coredns/coredns@sha256:8e352a029d304ca7431c6507b56800636c321cb52289686a581ab70aaa8a2e2a registry.k8s.io/coredns/coredns:v1.9.3],SizeBytes:14837849,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Nov 13 20:50:15.888: INFO:
Logging kubelet events for node capz-conf-m00n9c-control-plane-jvr6l
Nov 13 20:50:16.085: INFO:
Logging pods the kubelet thinks is on node capz-conf-m00n9c-control-plane-jvr6l
Nov 13 20:50:16.318: INFO: kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l started at <nil> (0+0 container statuses recorded)
Nov 13 20:50:16.318: INFO: metrics-server-c9574f845-scgh2 started at 2022-11-13 20:35:10 +0000 UTC (0+1 container statuses recorded)
Nov 13 20:50:16.318: INFO: Container metrics-server ready: true, restart count 0
Nov 13 20:50:16.318: INFO: coredns-787d4945fb-gk4nd started at 2022-11-13 20:35:10 +0000 UTC (0+1 container statuses recorded)
Nov 13 20:50:16.318: INFO: Container coredns ready: true, restart count 0
Nov 13 20:50:16.318: INFO: calico-kube-controllers-657b584867-8ptqc started at 2022-11-13 20:35:10 +0000 UTC (0+1 container statuses recorded)
Nov 13 20:50:16.318: INFO: Container calico-kube-controllers ready: true, restart count 0
Nov 13 20:50:16.318: INFO: etcd-capz-conf-m00n9c-control-plane-jvr6l started at 2022-11-13 20:34:39 +0000 UTC (0+1 container statuses recorded)
Nov 13 20:50:16.318: INFO: Container etcd ready: true, restart count 0
Nov 13 20:50:16.318: INFO: kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l started at <nil> (0+0 container statuses recorded)
Nov 13 20:50:16.318: INFO: kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l started at <nil> (0+0 container statuses recorded)
Nov 13 20:50:16.318: INFO: kube-proxy-lxvnh started at 2022-11-13 20:34:44 +0000 UTC (0+1 container statuses recorded)
Nov 13 20:50:16.318: INFO: Container kube-proxy ready: true, restart count 0
Nov 13 20:50:16.318: INFO: calico-node-zrz64 started at 2022-11-13 20:34:56 +0000 UTC (2+1 container statuses recorded)
Nov 13 20:50:16.318: INFO: Init container upgrade-ipam ready: true, restart count 0
Nov 13 20:50:16.318: INFO: Init container install-cni ready: true, restart count 0
Nov 13 20:50:16.318: INFO: Container calico-node ready: true, restart count 0
Nov 13 20:50:16.318: INFO: coredns-787d4945fb-wf2vr started at 2022-11-13 20:35:10 +0000 UTC (0+1 container statuses recorded)
Nov 13 20:50:16.318: INFO: Container coredns ready: true, restart count 0
Nov 13 20:50:16.925: INFO:
Latency metrics for node capz-conf-m00n9c-control-plane-jvr6l
Nov 13 20:50:17.094: INFO: Running kubectl logs on non-ready containers in kube-system
Nov 13 20:50:17.484: INFO: Failed to get logs of pod kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l)
Nov 13 20:50:17.484: INFO: Logs of kube-system/kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l:kube-apiserver on node capz-conf-m00n9c-control-plane-jvr6l
Nov 13 20:50:17.484: INFO: : STARTLOG
ENDLOG for container kube-system:kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l:kube-apiserver
Nov 13 20:50:17.884: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l)
Nov 13 20:50:17.884: INFO: Logs of kube-system/kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l:kube-controller-manager on node capz-conf-m00n9c-control-plane-jvr6l
Nov 13 20:50:17.884: INFO: : STARTLOG
ENDLOG for container kube-system:kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l:kube-controller-manager
Nov 13 20:50:18.283: INFO: Failed to get logs of pod kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l)
Nov 13 20:50:18.283: INFO: Logs of kube-system/kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l:kube-scheduler on node capz-conf-m00n9c-control-plane-jvr6l
Nov 13 20:50:18.283: INFO: : STARTLOG
ENDLOG for container kube-system:kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l:kube-scheduler
Nov 13 20:50:18.283: FAIL: Error waiting for all pods to be running and ready: 3 / 18 pods in namespace kube-system are NOT in RUNNING and READY state in 10m0s
POD NODE PHASE GRACE CONDITIONS
kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
Full Stack Trace
k8s.io/kubernetes/test/e2e.setupSuite({0x7f095c2dcb88, 0xc00336d3c0})
test/e2e/e2e.go:249 +0x5bf
k8s.io/kubernetes/test/e2e.glob..func1({0x7f095c2dcb88, 0xc00336d3c0})
test/e2e/e2e.go:81 +0xaa
reflect.Value.call({0x6856240?, 0x78af028?, 0x0?}, {0x75d139a, 0x4}, {0xc0000b5f38, 0x1, 0x0?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x6856240?, 0x78af028?, 0x0?}, {0xc0000b5f38?, 0x0?, 0x0?})
/usr/local/go/src/reflect/value.go:368 +0xbc
�[38;5;243m<< End Captured GinkgoWriter Output�[0m
�[38;5;9mNov 13 20:50:18.283: Error waiting for all pods to be running and ready: 3 / 18 pods in namespace kube-system are NOT in RUNNING and READY state in 10m0s
POD NODE PHASE GRACE CONDITIONS
kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l capz-conf-m00n9c-control-plane-jvr6l Pending []
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:249�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [606.240 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m�[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [606.206 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m�[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [606.173 seconds]�[0m
�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m�[1m�[38;5;9mSynchronizedBeforeSuite failed on Ginkgo parallel process #1�[0m
The first SynchronizedBeforeSuite function running on Ginkgo parallel process
#1 failed. This suite will now abort.
�[0m
�[38;5;9mIn �[1m[SynchronizedBeforeSuite]�[0m�[38;5;9m at: �[1mtest/e2e/e2e.go:77�[0m
�[38;5;243m------------------------------�[0m
�[38;5;9m�[1mSummarizing 4 Failures:�[0m
�[38;5;9m[FAIL]�[0m �[0m�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m�[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[0m�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m�[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[0m�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m�[0m
�[38;5;243mtest/e2e/e2e.go:77�[0m
�[38;5;9m[FAIL]�[0m �[0m�[38;5;9m�[1m[SynchronizedBeforeSuite] �[0m�[0m
�[38;5;243mtest/e2e/e2e.go:249�[0m
�[38;5;9m�[1mRan 0 of 7066 Specs in 606.265 seconds�[0m
�[38;5;9m�[1mFAIL!�[0m -- �[38;5;14m�[1mA BeforeSuite node failed so all tests were skipped.�[0m
I1113 20:40:11.547493 13 e2e.go:126] Starting e2e run "1229b4e9-dcbd-4379-b1c0-702de4cc63a8" on Ginkgo node 1
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.flakeAttempts is deprecated, use --ginkgo.flake-attempts instead�[0m
�[1mLearn more at:�[0m �[38;5;14m�[4mhttps://onsi.github.io/ginkgo/MIGRATING_TO_V2#changed-command-line-flags�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.4.0�[0m
--- FAIL: TestE2E (606.81s)
FAIL
I1113 20:40:11.536598 14 e2e.go:126] Starting e2e run "291b38b6-fe2b-4e50-9e27-6a1000865e6b" on Ginkgo node 2
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.flakeAttempts is deprecated, use --ginkgo.flake-attempts instead�[0m
�[1mLearn more at:�[0m �[38;5;14m�[4mhttps://onsi.github.io/ginkgo/MIGRATING_TO_V2#changed-command-line-flags�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.4.0�[0m
--- FAIL: TestE2E (606.80s)
FAIL
I1113 20:40:11.542050 16 e2e.go:126] Starting e2e run "d730f57a-383e-4898-b5d1-b731c2dc56b3" on Ginkgo node 3
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.flakeAttempts is deprecated, use --ginkgo.flake-attempts instead�[0m
�[1mLearn more at:�[0m �[38;5;14m�[4mhttps://onsi.github.io/ginkgo/MIGRATING_TO_V2#changed-command-line-flags�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.4.0�[0m
--- FAIL: TestE2E (606.79s)
FAIL
I1113 20:40:11.534215 17 e2e.go:126] Starting e2e run "59036742-e5fb-470e-80a5-62c9944bd461" on Ginkgo node 4
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--ginkgo.flakeAttempts is deprecated, use --ginkgo.flake-attempts instead�[0m
�[1mLearn more at:�[0m �[38;5;14m�[4mhttps://onsi.github.io/ginkgo/MIGRATING_TO_V2#changed-command-line-flags�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.4.0�[0m
--- FAIL: TestE2E (606.80s)
FAIL
Ginkgo ran 1 suite in 10m7.11132118s
Test Suite Failed
�[38;5;228mYou're using deprecated Ginkgo functionality:�[0m
�[38;5;228m=============================================�[0m
�[38;5;11m--slowSpecThreshold is deprecated use --slow-spec-threshold instead and pass in a duration string (e.g. '5s', not '5.0')�[0m
�[1mLearn more at:�[0m �[38;5;14m�[4mhttps://onsi.github.io/ginkgo/MIGRATING_TO_V2#changed--slowspecthreshold�[0m
�[38;5;243mTo silence deprecations that can be silenced set the following environment variable:�[0m
�[38;5;243mACK_GINKGO_DEPRECATIONS=2.4.0�[0m
[AfterEach] Conformance Tests
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:237
Nov 13 20:50:18.870: INFO: FAILED!
Nov 13 20:50:18.870: INFO: Cleaning up after "Conformance Tests conformance-tests" spec
�[1mSTEP�[0m: Dumping logs from the "capz-conf-m00n9c" workload cluster
�[1mSTEP�[0m: Dumping workload cluster capz-conf-m00n9c/capz-conf-m00n9c logs
Nov 13 20:50:18.919: INFO: Collecting logs for Linux node capz-conf-m00n9c-control-plane-jvr6l in cluster capz-conf-m00n9c in namespace capz-conf-m00n9c
Nov 13 20:50:32.861: INFO: Collecting boot logs for AzureMachine capz-conf-m00n9c-control-plane-jvr6l
Nov 13 20:50:34.797: INFO: Collecting logs for Windows node capz-conf-fs5d4 in cluster capz-conf-m00n9c in namespace capz-conf-m00n9c
Nov 13 20:53:04.908: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-fs5d4 to /logs/artifacts/clusters/capz-conf-m00n9c/machines/capz-conf-m00n9c-md-win-7d8fd48fdc-7kzww/crashdumps.tar
Nov 13 20:53:06.800: INFO: Collecting boot logs for AzureMachine capz-conf-m00n9c-md-win-fs5d4
Nov 13 20:53:07.564: INFO: Collecting logs for Windows node capz-conf-4qhqp in cluster capz-conf-m00n9c in namespace capz-conf-m00n9c
Nov 13 20:55:36.860: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-4qhqp to /logs/artifacts/clusters/capz-conf-m00n9c/machines/capz-conf-m00n9c-md-win-7d8fd48fdc-qzhzd/crashdumps.tar
Nov 13 20:55:38.687: INFO: Collecting boot logs for AzureMachine capz-conf-m00n9c-md-win-4qhqp
�[1mSTEP�[0m: Dumping workload cluster capz-conf-m00n9c/capz-conf-m00n9c kube-system pod logs
�[1mSTEP�[0m: Collecting events for Pod kube-system/calico-kube-controllers-657b584867-8ptqc
�[1mSTEP�[0m: Fetching kube-system pod logs took 421.477152ms
�[1mSTEP�[0m: Dumping workload cluster capz-conf-m00n9c/capz-conf-m00n9c Azure activity log
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-kube-controllers-657b584867-8ptqc, container calico-kube-controllers
�[1mSTEP�[0m: Collecting events for Pod kube-system/csi-proxy-dz98b
�[1mSTEP�[0m: Collecting events for Pod kube-system/etcd-capz-conf-m00n9c-control-plane-jvr6l
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l
�[1mSTEP�[0m: failed to find events of Pod "kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l"
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-windows-ql74d, container kube-proxy
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l, container kube-apiserver
�[1mSTEP�[0m: Creating log watcher for controller kube-system/containerd-logger-cbjfp, container containerd-logger
�[1mSTEP�[0m: Creating log watcher for controller kube-system/coredns-787d4945fb-gk4nd, container coredns
�[1mSTEP�[0m: Collecting events for Pod kube-system/coredns-787d4945fb-gk4nd
�[1mSTEP�[0m: Creating log watcher for controller kube-system/coredns-787d4945fb-wf2vr, container coredns
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-proxy-windows-ql74d
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l, container kube-scheduler
�[1mSTEP�[0m: Creating log watcher for controller kube-system/metrics-server-c9574f845-scgh2, container metrics-server
�[1mSTEP�[0m: failed to find events of Pod "etcd-capz-conf-m00n9c-control-plane-jvr6l"
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-proxy-lxvnh
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-windows-k2x9h, container calico-node-startup
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-windows-ldf97, container kube-proxy
�[1mSTEP�[0m: Creating log watcher for controller kube-system/csi-proxy-fk96m, container csi-proxy
�[1mSTEP�[0m: Collecting events for Pod kube-system/containerd-logger-cbjfp
�[1mSTEP�[0m: Creating log watcher for controller kube-system/containerd-logger-ct6l5, container containerd-logger
�[1mSTEP�[0m: Collecting events for Pod kube-system/coredns-787d4945fb-wf2vr
�[1mSTEP�[0m: Collecting events for Pod kube-system/metrics-server-c9574f845-scgh2
�[1mSTEP�[0m: Creating log watcher for controller kube-system/csi-proxy-dz98b, container csi-proxy
�[1mSTEP�[0m: Collecting events for Pod kube-system/containerd-logger-ct6l5
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l
�[1mSTEP�[0m: failed to find events of Pod "kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l"
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l, container kube-controller-manager
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-windows-k2x9h, container calico-node-felix
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-proxy-windows-ldf97
�[1mSTEP�[0m: Collecting events for Pod kube-system/csi-proxy-fk96m
�[1mSTEP�[0m: Creating log watcher for controller kube-system/etcd-capz-conf-m00n9c-control-plane-jvr6l, container etcd
�[1mSTEP�[0m: Collecting events for Pod kube-system/kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-windows-qq48l, container calico-node-startup
�[1mSTEP�[0m: failed to find events of Pod "kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l"
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-windows-qq48l, container calico-node-felix
�[1mSTEP�[0m: Creating log watcher for controller kube-system/calico-node-zrz64, container calico-node
�[1mSTEP�[0m: Collecting events for Pod kube-system/calico-node-zrz64
�[1mSTEP�[0m: Collecting events for Pod kube-system/calico-node-windows-qq48l
�[1mSTEP�[0m: Collecting events for Pod kube-system/calico-node-windows-k2x9h
�[1mSTEP�[0m: Creating log watcher for controller kube-system/kube-proxy-lxvnh, container kube-proxy
�[1mSTEP�[0m: Error starting logs stream for pod kube-system/kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l, container kube-apiserver: container "kube-apiserver" in pod "kube-apiserver-capz-conf-m00n9c-control-plane-jvr6l" is not available
�[1mSTEP�[0m: Error starting logs stream for pod kube-system/kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l, container kube-controller-manager: container "kube-controller-manager" in pod "kube-controller-manager-capz-conf-m00n9c-control-plane-jvr6l" is not available
�[1mSTEP�[0m: Error starting logs stream for pod kube-system/kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l, container kube-scheduler: container "kube-scheduler" in pod "kube-scheduler-capz-conf-m00n9c-control-plane-jvr6l" is not available
�[1mSTEP�[0m: Fetching activity logs took 4.055070994s
Nov 13 20:55:43.981: INFO: Dumping all the Cluster API resources in the "capz-conf-m00n9c" namespace
Nov 13 20:55:44.610: INFO: Deleting all clusters in the capz-conf-m00n9c namespace
�[1mSTEP�[0m: Deleting cluster capz-conf-m00n9c
INFO: Waiting for the Cluster capz-conf-m00n9c/capz-conf-m00n9c to be deleted
�[1mSTEP�[0m: Waiting for cluster capz-conf-m00n9c to be deleted
�[1mSTEP�[0m: Got error while streaming logs for pod kube-system/kube-proxy-windows-ql74d, container kube-proxy: unexpected EOF
�[1mSTEP�[0m: Got error while streaming logs for pod kube-system/containerd-logger-ct6l5, container containerd-logger: unexpected EOF
�[1mSTEP�[0m: Got error while streaming logs for pod kube-system/calico-node-windows-qq48l, container calico-node-startup: unexpected EOF
�[1mSTEP�[0m: Got error while streaming logs for pod kube-system/csi-proxy-fk96m, container csi-proxy: unexpected EOF
�[1mSTEP�[0m: Got error while streaming logs for pod kube-system/calico-node-windows-qq48l, container calico-node-felix: unexpected EOF
Nov 13 21:00:24.905: INFO: Deleting namespace used for hosting the "conformance-tests" test spec
INFO: Deleting namespace capz-conf-m00n9c
Nov 13 21:00:24.930: INFO: Checking if any resources are left over in Azure for spec "conformance-tests"
�[1mSTEP�[0m: Redacting sensitive information from logs
from junit.e2e_suite.1.xml
Filter through log files | View test history on testgrid
capz-e2e Running the Cluster API E2E tests API Version Upgrade upgrade from v1alpha4 to v1beta1, and scale workload clusters created in v1alpha4 Should create a management cluster and then upgrade all the providers
capz-e2e Running the Cluster API E2E tests Running KCP upgrade in a HA cluster [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Running KCP upgrade in a HA cluster using scale in rollout [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Running the MachineDeployment rollout spec Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
capz-e2e Running the Cluster API E2E tests Running the quick-start spec Should create a workload cluster
capz-e2e Running the Cluster API E2E tests Running the self-hosted spec Should pivot the bootstrap cluster to a self-hosted cluster
capz-e2e Running the Cluster API E2E tests Running the workload cluster upgrade spec [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Should successfully exercise machine pools Should successfully create a cluster with machine pool machines
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger machine deployment remediation
capz-e2e Running the Cluster API E2E tests Should successfully scale out and scale in a MachineDeployment Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count
capz-e2e Running the Cluster API E2E tests Should successfully set and use node drain timeout A node should be forcefully removed if it cannot be drained in time
capz-e2e Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] with a single control plane node and 1 node
capz-e2e Workload cluster creation Creating a VMSS cluster [REQUIRED] with a single control plane node and an AzureMachinePool with 2 Linux and 2 Windows worker nodes
capz-e2e Workload cluster creation Creating a cluster that uses the external cloud provider and external azurediskcsi driver [OPTIONAL] with a 1 control plane nodes and 2 worker nodes
capz-e2e Workload cluster creation Creating a dual-stack cluster [OPTIONAL] With dual-stack worker node
capz-e2e Workload cluster creation Creating a highly available cluster [REQUIRED] With 3 control-plane nodes and 2 Linux and 2 Windows worker nodes
capz-e2e Workload cluster creation Creating a ipv6 control-plane cluster [REQUIRED] With ipv6 worker node
capz-e2e Workload cluster creation Creating a private cluster [OPTIONAL] Creates a public management cluster in a custom vnet
capz-e2e Workload cluster creation Creating an AKS cluster [EXPERIMENTAL][Managed Kubernetes] with a single control plane node and 1 node
capz-e2e Workload cluster creation Creating clusters using clusterclass [OPTIONAL] with a single control plane node, one linux worker node, and one windows worker node
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=external CCM=external AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with intree cloud provider
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=external CCM=internal AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with intree cloud provider
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=internal CCM=internal AzureDiskCSIMigration=false: upgrade to v1.23 should create volumes dynamically with intree cloud provider
... 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 ... [37m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:99[0m [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 [1mSTEP[0m: 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: [1m1668372011[0m - will randomize all specs Will run [1m339[0m of [1m7066[0m specs Running in parallel across [1m4[0m processes [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [606.197 seconds][0m [38;5;9m[1m[SynchronizedBeforeSuite] [0m [38;5;243mtest/e2e/e2e.go:77[0m [38;5;243mBegin Captured GinkgoWriter Output >>[0m [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