PR #96120 pull-kubernetes-e2e-capz-windows-containerd #1592962853994762240
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| PR | LorbusChris: KEP 2258: add node log query |
| Result | ABORTED |
| Tests | 1 failed / 0 succeeded |
| Started | |
| Elapsed | 1h11m |
| Revision | 3f35818597cba94107a004fbcb355265fcceb717 |
| Refs |
96120 |
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 | 0xc000f12f78>: {
error: <*errors.withMessage | 0xc000b3e380>{
cause: <*errors.errorString | 0xc000dc88b0>{
s: "error container run failed with exit code 1",
},
msg: "Unable to run conformance tests",
},
stack: [0x2eed6f8, 0x32e5827, 0x1876cf7, 0x32e55f3, 0x14384c5, 0x14379bc, 0x187855c, 0x1879571, 0x1878f65, 0x18785fb, 0x187e889, 0x187e272, 0x188ab71, 0x188a896, 0x1889ee5, 0x188c5a5, 0x1899e09, 0x1899c1e, 0x32ea798, 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-spjmpp
�[1mSTEP�[0m: Creating namespace "capz-conf-spjmpp" for hosting the cluster
Nov 16 20:19:47.069: INFO: starting to create namespace for hosting the "capz-conf-spjmpp" test spec
INFO: Creating namespace capz-conf-spjmpp
INFO: Creating event watcher for namespace "capz-conf-spjmpp"
[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-spjmpp" using the "conformance-presubmit-artifacts-windows-containerd" template (Kubernetes v1.27.0-alpha.0.26+43b7a253539a77, 1 control-plane machines, 0 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster capz-conf-spjmpp --infrastructure (default) --kubernetes-version v1.27.0-alpha.0.26+43b7a253539a77 --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-spjmpp/capz-conf-spjmpp-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-spjmpp/capz-conf-spjmpp-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-spjmpp-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-spjmpp-md-win are in the "<None>" failure domain
INFO: Waiting for the machine pools to be provisioned
INFO: Using repo-list '' for version 'v1.27.0-alpha.0.26+43b7a253539a77'
�[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" "--" "--provider=skeleton" "--report-dir=/output" "--e2e-output-dir=/output/e2e-output" "--dump-logs-on-failure=false" "--report-prefix=kubetest." "--num-nodes=2" "--kubeconfig=/tmp/kubeconfig" "-ginkgo.trace=true" "-dump-logs-on-failure=true" "-ginkgo.focus=\\[Conformance\\]|\\[NodeConformance\\]|\\[sig-windows\\]|\\[sig-apps\\].CronJob|\\[sig-api-machinery\\].ResourceQuota|\\[sig-scheduling\\].SchedulerPreemption" "-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" "-ginkgo.slow-spec-threshold=120s" "-ginkgo.v=true" "-node-os-distro=windows" "-prepull-images=true" "-disable-log-dump=true" "-ginkgo.flakeAttempts=0" "-ginkgo.progress=true" "-ginkgo.timeout=3h"]
Running Suite: Kubernetes e2e suite - /usr/local/bin
====================================================
Random Seed: �[1m1668630522�[0m - will randomize all specs
Will run �[1m339�[0m of �[1m7073�[0m specs
Running in parallel across �[1m4�[0m processes
�[38;5;243m------------------------------�[0m
�[38;5;9m[SynchronizedBeforeSuite] [FAILED] [606.179 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 16 20:28:43.445: INFO: >>> kubeConfig: /tmp/kubeconfig
Nov 16 20:28:43.446: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Nov 16 20:28:43.648: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Nov 16 20:28:43.784: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:43.784: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:43.784: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:43.784: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Nov 16 20:28:43.784: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:28:43.784: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:28:43.784: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:43.784: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:43.784: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:43.784: INFO:
Nov 16 20:28:45.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:45.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:45.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:45.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Nov 16 20:28:45.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:28:45.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:28:45.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:45.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:45.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:45.913: INFO:
Nov 16 20:28:47.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:47.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:47.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:47.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Nov 16 20:28:47.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:28:47.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:28:47.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:47.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:47.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:47.911: INFO:
Nov 16 20:28:49.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:49.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:49.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:49.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Nov 16 20:28:49.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:28:49.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:28:49.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:49.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:49.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:49.917: INFO:
Nov 16 20:28:51.911: INFO: The status of Pod calico-node-windows-fl2zr is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:51.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:51.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:51.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:51.911: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Nov 16 20:28:51.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:28:51.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:28:51.911: INFO: calico-node-windows-fl2zr capz-conf-x9q7m Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:58 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:50 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:50 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }]
Nov 16 20:28:51.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:51.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:51.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:51.911: INFO:
Nov 16 20:28:53.917: INFO: The status of Pod calico-node-windows-fl2zr is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:53.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:53.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:53.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:53.917: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Nov 16 20:28:53.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:28:53.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:28:53.917: INFO: calico-node-windows-fl2zr capz-conf-x9q7m Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:58 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:50 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:50 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }]
Nov 16 20:28:53.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:53.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:53.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:53.917: INFO:
Nov 16 20:28:55.915: INFO: The status of Pod calico-node-windows-fl2zr is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:55.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:55.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:55.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:55.915: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Nov 16 20:28:55.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:28:55.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:28:55.915: INFO: calico-node-windows-fl2zr capz-conf-x9q7m Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:58 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:50 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:50 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }]
Nov 16 20:28:55.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:55.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:55.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:55.915: INFO:
Nov 16 20:28:57.915: INFO: The status of Pod calico-node-windows-fl2zr is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:57.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:57.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:57.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:57.915: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Nov 16 20:28:57.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:28:57.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:28:57.915: INFO: calico-node-windows-fl2zr capz-conf-x9q7m Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:58 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:50 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:50 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }]
Nov 16 20:28:57.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:57.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:57.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:57.915: INFO:
Nov 16 20:28:59.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:59.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:59.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:28:59.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Nov 16 20:28:59.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:28:59.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:28:59.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:59.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:59.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:28:59.915: INFO:
Nov 16 20:29:01.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:01.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:01.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:01.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Nov 16 20:29:01.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:01.910: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:01.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:01.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:01.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:01.910: INFO:
Nov 16 20:29:03.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:03.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:03.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:03.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Nov 16 20:29:03.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:03.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:03.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:03.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:03.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:03.915: INFO:
Nov 16 20:29:05.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:05.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:05.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:05.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Nov 16 20:29:05.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:05.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:05.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:05.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:05.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:05.920: INFO:
Nov 16 20:29:07.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:07.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:07.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:07.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Nov 16 20:29:07.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:07.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:07.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:07.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:07.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:07.915: INFO:
Nov 16 20:29:09.917: INFO: The status of Pod calico-node-windows-rqv4b is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:09.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:09.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:09.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:09.917: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Nov 16 20:29:09.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:09.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:09.917: INFO: calico-node-windows-rqv4b capz-conf-mq8ck Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:22 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:29:08 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:29:08 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }]
Nov 16 20:29:09.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:09.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:09.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:09.917: INFO:
Nov 16 20:29:11.917: INFO: The status of Pod calico-node-windows-rqv4b is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:11.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:11.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:11.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:11.917: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Nov 16 20:29:11.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:11.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:11.917: INFO: calico-node-windows-rqv4b capz-conf-mq8ck Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:22 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:29:08 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:29:08 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }]
Nov 16 20:29:11.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:11.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:11.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:11.917: INFO:
Nov 16 20:29:13.915: INFO: The status of Pod calico-node-windows-rqv4b is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:13.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:13.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:13.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:13.915: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
Nov 16 20:29:13.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:13.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:13.915: INFO: calico-node-windows-rqv4b capz-conf-mq8ck Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:22 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:29:08 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:29:08 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }]
Nov 16 20:29:13.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:13.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:13.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:13.915: INFO:
Nov 16 20:29:15.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:15.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:15.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:15.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
Nov 16 20:29:15.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:15.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:15.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:15.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:15.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:15.914: INFO:
Nov 16 20:29:17.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:17.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:17.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:17.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed)
Nov 16 20:29:17.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:17.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:17.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:17.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:17.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:17.915: INFO:
Nov 16 20:29:19.921: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:19.921: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:19.921: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:19.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed)
Nov 16 20:29:19.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:19.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:19.921: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:19.921: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:19.921: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:19.921: INFO:
Nov 16 20:29:21.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:21.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:21.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:21.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed)
Nov 16 20:29:21.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:21.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:21.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:21.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:21.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:21.915: INFO:
Nov 16 20:29:23.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:23.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:23.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:23.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed)
Nov 16 20:29:23.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:23.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:23.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:23.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:23.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:23.911: INFO:
Nov 16 20:29:25.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:25.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:25.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:25.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed)
Nov 16 20:29:25.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:25.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:25.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:25.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:25.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:25.913: INFO:
Nov 16 20:29:27.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:27.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:27.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:27.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed)
Nov 16 20:29:27.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:27.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:27.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:27.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:27.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:27.912: INFO:
Nov 16 20:29:29.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:29.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:29.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:29.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed)
Nov 16 20:29:29.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:29.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:29.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:29.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:29.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:29.913: INFO:
Nov 16 20:29:31.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:31.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:31.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:31.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed)
Nov 16 20:29:31.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:31.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:31.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:31.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:31.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:31.914: INFO:
Nov 16 20:29:33.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:33.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:33.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:33.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed)
Nov 16 20:29:33.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:33.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:33.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:33.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:33.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:33.912: INFO:
Nov 16 20:29:35.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:35.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:35.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:35.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed)
Nov 16 20:29:35.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:35.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:35.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:35.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:35.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:35.914: INFO:
Nov 16 20:29:37.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:37.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:37.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:37.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed)
Nov 16 20:29:37.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:37.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:37.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:37.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:37.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:37.914: INFO:
Nov 16 20:29:39.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:39.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:39.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:39.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed)
Nov 16 20:29:39.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:39.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:39.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:39.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:39.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:39.915: INFO:
Nov 16 20:29:41.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:41.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:41.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:41.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed)
Nov 16 20:29:41.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:41.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:41.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:41.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:41.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:41.913: INFO:
Nov 16 20:29:43.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:43.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:43.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:43.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed)
Nov 16 20:29:43.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:43.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:43.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:43.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:43.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:43.912: INFO:
Nov 16 20:29:45.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:45.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:45.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:45.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed)
Nov 16 20:29:45.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:45.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:45.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:45.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:45.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:45.920: INFO:
Nov 16 20:29:47.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:47.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:47.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:47.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed)
Nov 16 20:29:47.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:47.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:47.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:47.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:47.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:47.911: INFO:
Nov 16 20:29:49.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:49.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:49.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:49.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed)
Nov 16 20:29:49.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:49.910: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:49.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:49.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:49.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:49.910: INFO:
Nov 16 20:29:51.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:51.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:51.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:51.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed)
Nov 16 20:29:51.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:51.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:51.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:51.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:51.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:51.913: INFO:
Nov 16 20:29:53.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:53.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:53.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:53.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed)
Nov 16 20:29:53.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:53.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:53.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:53.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:53.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:53.912: INFO:
Nov 16 20:29:55.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:55.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:55.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:55.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed)
Nov 16 20:29:55.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:55.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:55.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:55.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:55.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:55.913: INFO:
Nov 16 20:29:57.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:57.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:57.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:57.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed)
Nov 16 20:29:57.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:57.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:57.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:57.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:57.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:57.912: INFO:
Nov 16 20:29:59.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:59.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:59.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:29:59.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed)
Nov 16 20:29:59.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:29:59.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:29:59.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:59.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:59.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:29:59.915: INFO:
Nov 16 20:30:01.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:01.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:01.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:01.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed)
Nov 16 20:30:01.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:01.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:01.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:01.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:01.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:01.913: INFO:
Nov 16 20:30:03.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:03.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:03.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:03.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed)
Nov 16 20:30:03.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:03.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:03.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:03.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:03.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:03.913: INFO:
Nov 16 20:30:05.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:05.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:05.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:05.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed)
Nov 16 20:30:05.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:05.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:05.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:05.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:05.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:05.914: INFO:
Nov 16 20:30:07.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:07.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:07.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:07.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed)
Nov 16 20:30:07.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:07.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:07.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:07.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:07.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:07.916: INFO:
Nov 16 20:30:09.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:09.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:09.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:09.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed)
Nov 16 20:30:09.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:09.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:09.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:09.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:09.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:09.916: INFO:
Nov 16 20:30:11.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:11.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:11.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:11.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed)
Nov 16 20:30:11.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:11.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:11.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:11.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:11.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:11.920: INFO:
Nov 16 20:30:13.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:13.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:13.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:13.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed)
Nov 16 20:30:13.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:13.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:13.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:13.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:13.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:13.913: INFO:
Nov 16 20:30:15.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:15.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:15.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:15.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed)
Nov 16 20:30:15.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:15.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:15.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:15.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:15.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:15.912: INFO:
Nov 16 20:30:17.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:17.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:17.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:17.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed)
Nov 16 20:30:17.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:17.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:17.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:17.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:17.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:17.913: INFO:
Nov 16 20:30:19.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:19.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:19.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:19.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed)
Nov 16 20:30:19.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:19.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:19.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:19.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:19.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:19.913: INFO:
Nov 16 20:30:22.022: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:22.022: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:22.022: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:22.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed)
Nov 16 20:30:22.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:22.022: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:22.022: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:22.022: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:22.022: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:22.022: INFO:
Nov 16 20:30:23.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:23.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:23.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:23.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed)
Nov 16 20:30:23.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:23.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:23.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:23.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:23.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:23.911: INFO:
Nov 16 20:30:25.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:25.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:25.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:25.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed)
Nov 16 20:30:25.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:25.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:25.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:25.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:25.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:25.911: INFO:
Nov 16 20:30:27.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:27.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:27.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:27.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed)
Nov 16 20:30:27.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:27.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:27.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:27.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:27.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:27.913: INFO:
Nov 16 20:30:29.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:29.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:29.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:29.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed)
Nov 16 20:30:29.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:29.910: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:29.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:29.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:29.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:29.910: INFO:
Nov 16 20:30:31.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:31.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:31.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:31.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed)
Nov 16 20:30:31.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:31.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:31.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:31.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:31.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:31.911: INFO:
Nov 16 20:30:33.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:33.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:33.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:33.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed)
Nov 16 20:30:33.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:33.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:33.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:33.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:33.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:33.918: INFO:
Nov 16 20:30:35.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:35.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:35.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:35.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed)
Nov 16 20:30:35.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:35.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:35.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:35.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:35.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:35.918: INFO:
Nov 16 20:30:37.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:37.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:37.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:37.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed)
Nov 16 20:30:37.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:37.910: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:37.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:37.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:37.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:37.910: INFO:
Nov 16 20:30:39.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:39.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:39.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:39.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed)
Nov 16 20:30:39.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:39.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:39.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:39.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:39.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:39.919: INFO:
Nov 16 20:30:41.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:41.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:41.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:41.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed)
Nov 16 20:30:41.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:41.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:41.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:41.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:41.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:41.916: INFO:
Nov 16 20:30:43.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:43.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:43.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:43.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed)
Nov 16 20:30:43.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:43.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:43.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:43.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:43.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:43.911: INFO:
Nov 16 20:30:45.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:45.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:45.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:45.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed)
Nov 16 20:30:45.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:45.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:45.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:45.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:45.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:45.917: INFO:
Nov 16 20:30:47.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:47.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:47.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:47.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed)
Nov 16 20:30:47.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:47.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:47.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:47.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:47.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:47.915: INFO:
Nov 16 20:30:49.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:49.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:49.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:49.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed)
Nov 16 20:30:49.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:49.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:49.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:49.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:49.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:49.913: INFO:
Nov 16 20:30:51.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:51.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:51.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:51.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed)
Nov 16 20:30:51.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:51.910: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:51.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:51.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:51.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:51.910: INFO:
Nov 16 20:30:53.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:53.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:53.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:53.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed)
Nov 16 20:30:53.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:53.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:53.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:53.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:53.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:53.913: INFO:
Nov 16 20:30:55.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:55.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:55.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:55.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed)
Nov 16 20:30:55.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:55.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:55.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:55.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:55.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:55.913: INFO:
Nov 16 20:30:57.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:57.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:57.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:57.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed)
Nov 16 20:30:57.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:57.910: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:57.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:57.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:57.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:57.910: INFO:
Nov 16 20:30:59.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:59.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:59.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:30:59.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed)
Nov 16 20:30:59.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:30:59.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:30:59.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:59.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:59.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:30:59.912: INFO:
Nov 16 20:31:01.923: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:01.923: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:01.923: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:01.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed)
Nov 16 20:31:01.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:01.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:01.923: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:01.923: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:01.923: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:01.923: INFO:
Nov 16 20:31:03.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:03.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:03.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:03.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed)
Nov 16 20:31:03.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:03.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:03.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:03.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:03.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:03.914: INFO:
Nov 16 20:31:05.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:05.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:05.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:05.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed)
Nov 16 20:31:05.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:05.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:05.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:05.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:05.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:05.915: INFO:
Nov 16 20:31:07.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:07.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:07.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:07.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed)
Nov 16 20:31:07.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:07.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:07.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:07.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:07.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:07.918: INFO:
Nov 16 20:31:09.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:09.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:09.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:09.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed)
Nov 16 20:31:09.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:09.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:09.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:09.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:09.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:09.913: INFO:
Nov 16 20:31:11.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:11.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:11.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:11.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed)
Nov 16 20:31:11.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:11.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:11.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:11.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:11.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:11.911: INFO:
Nov 16 20:31:13.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:13.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:13.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:13.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed)
Nov 16 20:31:13.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:13.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:13.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:13.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:13.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:13.913: INFO:
Nov 16 20:31:15.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:15.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:15.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:15.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed)
Nov 16 20:31:15.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:15.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:15.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:15.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:15.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:15.914: INFO:
Nov 16 20:31:17.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:17.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:17.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:17.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed)
Nov 16 20:31:17.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:17.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:17.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:17.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:17.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:17.914: INFO:
Nov 16 20:31:19.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:19.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:19.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:19.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed)
Nov 16 20:31:19.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:19.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:19.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:19.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:19.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:19.916: INFO:
Nov 16 20:31:21.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:21.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:21.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:21.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed)
Nov 16 20:31:21.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:21.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:21.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:21.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:21.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:21.914: INFO:
Nov 16 20:31:23.921: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:23.921: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:23.921: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:23.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed)
Nov 16 20:31:23.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:23.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:23.921: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:23.921: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:23.921: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:23.921: INFO:
Nov 16 20:31:25.926: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:25.926: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:25.926: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:25.926: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed)
Nov 16 20:31:25.926: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:25.926: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:25.926: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:25.926: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:25.926: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:25.926: INFO:
Nov 16 20:31:27.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:27.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:27.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:27.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed)
Nov 16 20:31:27.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:27.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:27.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:27.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:27.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:27.915: INFO:
Nov 16 20:31:29.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:29.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:29.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:29.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed)
Nov 16 20:31:29.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:29.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:29.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:29.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:29.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:29.917: INFO:
Nov 16 20:31:31.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:31.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:31.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:31.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed)
Nov 16 20:31:31.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:31.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:31.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:31.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:31.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:31.911: INFO:
Nov 16 20:31:33.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:33.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:33.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:33.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed)
Nov 16 20:31:33.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:33.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:33.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:33.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:33.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:33.915: INFO:
Nov 16 20:31:35.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:35.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:35.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:35.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed)
Nov 16 20:31:35.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:35.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:35.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:35.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:35.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:35.912: INFO:
Nov 16 20:31:37.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:37.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:37.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:37.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed)
Nov 16 20:31:37.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:37.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:37.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:37.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:37.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:37.913: INFO:
Nov 16 20:31:39.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:39.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:39.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:39.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed)
Nov 16 20:31:39.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:39.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:39.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:39.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:39.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:39.915: INFO:
Nov 16 20:31:41.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:41.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:41.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:41.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed)
Nov 16 20:31:41.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:41.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:41.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:41.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:41.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:41.914: INFO:
Nov 16 20:31:43.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:43.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:43.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:43.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed)
Nov 16 20:31:43.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:43.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:43.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:43.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:43.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:43.919: INFO:
Nov 16 20:31:45.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:45.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:45.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:45.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed)
Nov 16 20:31:45.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:45.910: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:45.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:45.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:45.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:45.910: INFO:
Nov 16 20:31:47.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:47.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:47.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:47.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed)
Nov 16 20:31:47.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:47.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:47.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:47.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:47.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:47.911: INFO:
Nov 16 20:31:49.931: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:49.931: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:49.931: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:49.931: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed)
Nov 16 20:31:49.931: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:49.931: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:49.931: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:49.931: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:49.931: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:49.931: INFO:
Nov 16 20:31:51.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:51.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:51.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:51.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed)
Nov 16 20:31:51.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:51.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:51.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:51.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:51.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:51.912: INFO:
Nov 16 20:31:53.923: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:53.923: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:53.923: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:53.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed)
Nov 16 20:31:53.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:53.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:53.923: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:53.923: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:53.923: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:53.923: INFO:
Nov 16 20:31:55.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:55.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:55.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:55.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed)
Nov 16 20:31:55.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:55.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:55.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:55.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:55.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:55.913: INFO:
Nov 16 20:31:57.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:57.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:57.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:57.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed)
Nov 16 20:31:57.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:57.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:57.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:57.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:57.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:57.911: INFO:
Nov 16 20:31:59.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:59.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:59.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:31:59.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed)
Nov 16 20:31:59.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:31:59.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:31:59.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:59.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:59.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:31:59.912: INFO:
Nov 16 20:32:01.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:01.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:01.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:01.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed)
Nov 16 20:32:01.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:01.910: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:01.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:01.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:01.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:01.910: INFO:
Nov 16 20:32:03.958: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:03.958: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:03.958: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:03.958: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed)
Nov 16 20:32:03.958: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:03.958: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:03.958: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:03.958: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:03.958: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:03.958: INFO:
Nov 16 20:32:05.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:05.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:05.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:05.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed)
Nov 16 20:32:05.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:05.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:05.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:05.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:05.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:05.914: INFO:
Nov 16 20:32:07.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:07.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:07.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:07.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed)
Nov 16 20:32:07.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:07.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:07.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:07.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:07.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:07.912: INFO:
Nov 16 20:32:09.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:09.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:09.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:09.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed)
Nov 16 20:32:09.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:09.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:09.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:09.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:09.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:09.912: INFO:
Nov 16 20:32:11.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:11.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:11.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:11.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed)
Nov 16 20:32:11.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:11.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:11.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:11.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:11.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:11.915: INFO:
Nov 16 20:32:13.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:13.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:13.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:13.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed)
Nov 16 20:32:13.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:13.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:13.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:13.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:13.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:13.912: INFO:
Nov 16 20:32:15.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:15.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:15.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:15.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed)
Nov 16 20:32:15.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:15.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:15.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:15.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:15.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:15.913: INFO:
Nov 16 20:32:17.926: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:17.926: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:17.926: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:17.926: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed)
Nov 16 20:32:17.926: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:17.926: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:17.926: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:17.926: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:17.926: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:17.926: INFO:
Nov 16 20:32:19.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:19.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:19.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:19.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed)
Nov 16 20:32:19.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:19.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:19.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:19.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:19.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:19.913: INFO:
Nov 16 20:32:21.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:21.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:21.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:21.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed)
Nov 16 20:32:21.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:21.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:21.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:21.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:21.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:21.911: INFO:
Nov 16 20:32:23.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:23.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:23.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:23.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed)
Nov 16 20:32:23.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:23.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:23.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:23.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:23.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:23.912: INFO:
Nov 16 20:32:25.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:25.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:25.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:25.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed)
Nov 16 20:32:25.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:25.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:25.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:25.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:25.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:25.917: INFO:
Nov 16 20:32:27.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:27.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:27.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:27.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed)
Nov 16 20:32:27.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:27.910: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:27.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:27.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:27.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:27.910: INFO:
Nov 16 20:32:29.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:29.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:29.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:29.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed)
Nov 16 20:32:29.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:29.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:29.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:29.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:29.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:29.916: INFO:
Nov 16 20:32:32.023: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:32.023: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:32.023: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:32.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed)
Nov 16 20:32:32.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:32.023: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:32.023: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:32.023: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:32.023: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:32.023: INFO:
Nov 16 20:32:33.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:33.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:33.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:33.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed)
Nov 16 20:32:33.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:33.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:33.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:33.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:33.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:33.918: INFO:
Nov 16 20:32:35.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:35.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:35.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:35.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed)
Nov 16 20:32:35.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:35.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:35.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:35.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:35.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:35.914: INFO:
Nov 16 20:32:37.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:37.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:37.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:37.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed)
Nov 16 20:32:37.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:37.910: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:37.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:37.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:37.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:37.910: INFO:
Nov 16 20:32:39.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:39.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:39.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:39.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed)
Nov 16 20:32:39.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:39.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:39.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:39.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:39.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:39.912: INFO:
Nov 16 20:32:41.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:41.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:41.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:41.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed)
Nov 16 20:32:41.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:41.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:41.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:41.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:41.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:41.912: INFO:
Nov 16 20:32:43.931: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:43.931: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:43.931: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:43.931: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed)
Nov 16 20:32:43.931: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:43.931: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:43.931: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:43.931: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:43.931: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:43.931: INFO:
Nov 16 20:32:45.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:45.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:45.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:45.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed)
Nov 16 20:32:45.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:45.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:45.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:45.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:45.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:45.914: INFO:
Nov 16 20:32:47.942: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:47.942: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:47.942: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:47.942: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed)
Nov 16 20:32:47.942: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:47.942: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:47.942: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:47.942: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:47.942: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:47.942: INFO:
Nov 16 20:32:49.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:49.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:49.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:49.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed)
Nov 16 20:32:49.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:49.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:49.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:49.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:49.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:49.912: INFO:
Nov 16 20:32:51.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:51.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:51.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:51.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed)
Nov 16 20:32:51.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:51.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:51.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:51.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:51.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:51.912: INFO:
Nov 16 20:32:53.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:53.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:53.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:53.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed)
Nov 16 20:32:53.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:53.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:53.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:53.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:53.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:53.915: INFO:
Nov 16 20:32:55.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:55.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:55.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:55.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed)
Nov 16 20:32:55.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:55.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:55.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:55.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:55.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:55.913: INFO:
Nov 16 20:32:57.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:57.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:57.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:57.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed)
Nov 16 20:32:57.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:57.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:57.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:57.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:57.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:57.916: INFO:
Nov 16 20:32:59.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:59.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:59.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:32:59.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed)
Nov 16 20:32:59.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:32:59.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:32:59.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:59.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:59.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:32:59.911: INFO:
Nov 16 20:33:01.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:01.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:01.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:01.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed)
Nov 16 20:33:01.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:01.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:01.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:01.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:01.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:01.922: INFO:
Nov 16 20:33:03.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:03.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:03.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:03.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed)
Nov 16 20:33:03.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:03.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:03.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:03.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:03.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:03.912: INFO:
Nov 16 20:33:05.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:05.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:05.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:05.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed)
Nov 16 20:33:05.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:05.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:05.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:05.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:05.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:05.917: INFO:
Nov 16 20:33:07.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:07.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:07.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:07.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed)
Nov 16 20:33:07.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:07.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:07.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:07.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:07.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:07.913: INFO:
Nov 16 20:33:09.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:09.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:09.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:09.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed)
Nov 16 20:33:09.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:09.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:09.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:09.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:09.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:09.913: INFO:
Nov 16 20:33:11.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:11.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:11.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:11.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed)
Nov 16 20:33:11.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:11.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:11.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:11.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:11.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:11.913: INFO:
Nov 16 20:33:13.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:13.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:13.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:13.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed)
Nov 16 20:33:13.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:13.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:13.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:13.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:13.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:13.913: INFO:
Nov 16 20:33:15.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:15.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:15.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:15.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed)
Nov 16 20:33:15.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:15.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:15.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:15.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:15.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:15.919: INFO:
Nov 16 20:33:17.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:17.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:17.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:17.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed)
Nov 16 20:33:17.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:17.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:17.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:17.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:17.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:17.914: INFO:
Nov 16 20:33:19.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:19.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:19.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:19.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed)
Nov 16 20:33:19.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:19.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:19.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:19.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:19.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:19.912: INFO:
Nov 16 20:33:21.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:21.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:21.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:21.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed)
Nov 16 20:33:21.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:21.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:21.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:21.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:21.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:21.915: INFO:
Nov 16 20:33:23.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:23.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:23.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:23.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed)
Nov 16 20:33:23.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:23.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:23.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:23.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:23.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:23.914: INFO:
Nov 16 20:33:25.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:25.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:25.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:25.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed)
Nov 16 20:33:25.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:25.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:25.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:25.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:25.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:25.913: INFO:
Nov 16 20:33:27.909: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:27.909: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:27.909: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:27.909: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed)
Nov 16 20:33:27.909: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:27.909: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:27.909: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:27.909: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:27.909: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:27.909: INFO:
Nov 16 20:33:29.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:29.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:29.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:29.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed)
Nov 16 20:33:29.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:29.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:29.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:29.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:29.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:29.913: INFO:
Nov 16 20:33:31.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:31.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:31.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:31.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed)
Nov 16 20:33:31.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:31.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:31.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:31.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:31.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:31.913: INFO:
Nov 16 20:33:33.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:33.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:33.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:33.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed)
Nov 16 20:33:33.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:33.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:33.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:33.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:33.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:33.911: INFO:
Nov 16 20:33:35.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:35.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:35.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:35.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed)
Nov 16 20:33:35.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:35.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:35.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:35.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:35.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:35.915: INFO:
Nov 16 20:33:37.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:37.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:37.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:37.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed)
Nov 16 20:33:37.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:37.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:37.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:37.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:37.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:37.914: INFO:
Nov 16 20:33:39.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:39.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:39.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:39.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed)
Nov 16 20:33:39.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:39.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:39.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:39.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:39.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:39.911: INFO:
Nov 16 20:33:41.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:41.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:41.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:41.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed)
Nov 16 20:33:41.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:41.910: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:41.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:41.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:41.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:41.910: INFO:
Nov 16 20:33:43.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:43.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:43.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:43.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed)
Nov 16 20:33:43.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:43.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:43.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:43.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:43.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:43.914: INFO:
Nov 16 20:33:45.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:45.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:45.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:45.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed)
Nov 16 20:33:45.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:45.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:45.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:45.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:45.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:45.914: INFO:
Nov 16 20:33:47.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:47.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:47.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:47.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed)
Nov 16 20:33:47.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:47.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:47.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:47.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:47.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:47.914: INFO:
Nov 16 20:33:49.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:49.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:49.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:49.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed)
Nov 16 20:33:49.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:49.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:49.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:49.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:49.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:49.912: INFO:
Nov 16 20:33:51.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:51.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:51.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:51.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed)
Nov 16 20:33:51.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:51.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:51.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:51.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:51.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:51.912: INFO:
Nov 16 20:33:53.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:53.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:53.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:53.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed)
Nov 16 20:33:53.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:53.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:53.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:53.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:53.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:53.916: INFO:
Nov 16 20:33:55.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:55.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:55.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:55.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed)
Nov 16 20:33:55.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:55.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:55.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:55.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:55.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:55.911: INFO:
Nov 16 20:33:57.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:57.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:57.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:57.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed)
Nov 16 20:33:57.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:57.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:57.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:57.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:57.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:57.914: INFO:
Nov 16 20:33:59.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:59.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:59.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:33:59.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed)
Nov 16 20:33:59.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:33:59.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:33:59.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:59.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:59.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:33:59.912: INFO:
Nov 16 20:34:01.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:01.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:01.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:01.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed)
Nov 16 20:34:01.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:01.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:01.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:01.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:01.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:01.913: INFO:
Nov 16 20:34:03.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:03.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:03.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:03.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed)
Nov 16 20:34:03.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:03.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:03.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:03.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:03.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:03.912: INFO:
Nov 16 20:34:05.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:05.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:05.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:05.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed)
Nov 16 20:34:05.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:05.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:05.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:05.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:05.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:05.913: INFO:
Nov 16 20:34:07.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:07.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:07.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:07.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed)
Nov 16 20:34:07.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:07.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:07.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:07.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:07.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:07.911: INFO:
Nov 16 20:34:09.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:09.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:09.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:09.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed)
Nov 16 20:34:09.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:09.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:09.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:09.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:09.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:09.911: INFO:
Nov 16 20:34:11.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:11.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:11.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:11.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed)
Nov 16 20:34:11.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:11.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:11.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:11.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:11.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:11.911: INFO:
Nov 16 20:34:13.926: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:13.926: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:13.926: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:13.926: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed)
Nov 16 20:34:13.926: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:13.926: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:13.926: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:13.926: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:13.926: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:13.926: INFO:
Nov 16 20:34:15.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:15.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:15.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:15.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed)
Nov 16 20:34:15.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:15.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:15.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:15.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:15.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:15.915: INFO:
Nov 16 20:34:17.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:17.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:17.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:17.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed)
Nov 16 20:34:17.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:17.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:17.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:17.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:17.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:17.912: INFO:
Nov 16 20:34:19.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:19.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:19.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:19.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed)
Nov 16 20:34:19.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:19.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:19.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:19.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:19.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:19.917: INFO:
Nov 16 20:34:21.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:21.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:21.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:21.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed)
Nov 16 20:34:21.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:21.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:21.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:21.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:21.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:21.917: INFO:
Nov 16 20:34:23.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:23.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:23.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:23.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed)
Nov 16 20:34:23.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:23.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:23.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:23.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:23.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:23.913: INFO:
Nov 16 20:34:25.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:25.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:25.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:25.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed)
Nov 16 20:34:25.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:25.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:25.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:25.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:25.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:25.913: INFO:
Nov 16 20:34:27.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:27.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:27.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:27.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed)
Nov 16 20:34:27.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:27.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:27.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:27.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:27.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:27.914: INFO:
Nov 16 20:34:29.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:29.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:29.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:29.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed)
Nov 16 20:34:29.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:29.910: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:29.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:29.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:29.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:29.910: INFO:
Nov 16 20:34:31.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:31.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:31.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:31.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed)
Nov 16 20:34:31.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:31.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:31.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:31.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:31.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:31.911: INFO:
Nov 16 20:34:33.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:33.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:33.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:33.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed)
Nov 16 20:34:33.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:33.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:33.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:33.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:33.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:33.912: INFO:
Nov 16 20:34:35.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:35.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:35.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:35.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed)
Nov 16 20:34:35.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:35.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:35.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:35.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:35.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:35.913: INFO:
Nov 16 20:34:37.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:37.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:37.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:37.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed)
Nov 16 20:34:37.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:37.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:37.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:37.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:37.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:37.914: INFO:
Nov 16 20:34:39.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:39.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:39.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:39.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed)
Nov 16 20:34:39.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:39.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:39.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:39.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:39.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:39.912: INFO:
Nov 16 20:34:41.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:41.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:41.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:41.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed)
Nov 16 20:34:41.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:41.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:41.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:41.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:41.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:41.912: INFO:
Nov 16 20:34:43.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:43.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:43.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:43.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (360 seconds elapsed)
Nov 16 20:34:43.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:43.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:43.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:43.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:43.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:43.912: INFO:
Nov 16 20:34:45.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:45.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:45.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:45.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed)
Nov 16 20:34:45.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:45.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:45.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:45.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:45.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:45.916: INFO:
Nov 16 20:34:47.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:47.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:47.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:47.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed)
Nov 16 20:34:47.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:47.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:47.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:47.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:47.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:47.915: INFO:
Nov 16 20:34:49.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:49.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:49.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:49.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed)
Nov 16 20:34:49.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:49.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:49.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:49.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:49.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:49.912: INFO:
Nov 16 20:34:51.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:51.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:51.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:51.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed)
Nov 16 20:34:51.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:51.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:51.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:51.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:51.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:51.913: INFO:
Nov 16 20:34:53.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:53.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:53.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:53.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed)
Nov 16 20:34:53.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:53.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:53.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:53.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:53.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:53.915: INFO:
Nov 16 20:34:55.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:55.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:55.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:55.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed)
Nov 16 20:34:55.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:55.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:55.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:55.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:55.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:55.915: INFO:
Nov 16 20:34:57.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:57.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:57.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:57.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed)
Nov 16 20:34:57.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:57.910: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:57.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:57.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:57.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:57.910: INFO:
Nov 16 20:34:59.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:59.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:59.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:34:59.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed)
Nov 16 20:34:59.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:34:59.910: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:34:59.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:59.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:59.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:34:59.910: INFO:
Nov 16 20:35:01.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:01.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:01.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:01.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed)
Nov 16 20:35:01.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:01.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:01.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:01.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:01.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:01.914: INFO:
Nov 16 20:35:03.921: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:03.921: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:03.921: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:03.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed)
Nov 16 20:35:03.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:03.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:03.921: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:03.921: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:03.921: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:03.921: INFO:
Nov 16 20:35:05.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:05.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:05.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:05.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed)
Nov 16 20:35:05.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:05.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:05.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:05.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:05.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:05.913: INFO:
Nov 16 20:35:07.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:07.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:07.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:07.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed)
Nov 16 20:35:07.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:07.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:07.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:07.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:07.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:07.911: INFO:
Nov 16 20:35:09.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:09.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:09.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:09.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed)
Nov 16 20:35:09.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:09.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:09.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:09.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:09.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:09.913: INFO:
Nov 16 20:35:11.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:11.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:11.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:11.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed)
Nov 16 20:35:11.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:11.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:11.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:11.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:11.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:11.911: INFO:
Nov 16 20:35:13.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:13.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:13.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:13.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed)
Nov 16 20:35:13.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:13.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:13.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:13.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:13.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:13.912: INFO:
Nov 16 20:35:15.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:15.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:15.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:15.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed)
Nov 16 20:35:15.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:15.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:15.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:15.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:15.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:15.911: INFO:
Nov 16 20:35:17.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:17.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:17.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:17.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed)
Nov 16 20:35:17.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:17.910: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:17.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:17.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:17.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:17.910: INFO:
Nov 16 20:35:19.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:19.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:19.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:19.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed)
Nov 16 20:35:19.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:19.911: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:19.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:19.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:19.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:19.911: INFO:
Nov 16 20:35:21.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:21.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:21.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:21.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed)
Nov 16 20:35:21.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:21.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:21.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:21.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:21.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:21.912: INFO:
Nov 16 20:35:23.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:23.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:23.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:23.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed)
Nov 16 20:35:23.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:23.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:23.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:23.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:23.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:23.913: INFO:
Nov 16 20:35:25.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:25.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:25.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:25.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed)
Nov 16 20:35:25.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:25.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:25.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:25.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:25.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:25.915: INFO:
Nov 16 20:35:27.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:27.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:27.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:27.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed)
Nov 16 20:35:27.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:27.912: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:27.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:27.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:27.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:27.912: INFO:
Nov 16 20:35:29.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:29.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:29.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:29.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed)
Nov 16 20:35:29.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:29.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:29.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:29.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:29.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:29.918: INFO:
Nov 16 20:35:31.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:31.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:31.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:31.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed)
Nov 16 20:35:31.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:31.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:31.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:31.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:31.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:31.913: INFO:
Nov 16 20:35:33.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:33.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:33.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:33.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed)
Nov 16 20:35:33.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:33.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:33.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:33.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:33.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:33.919: INFO:
Nov 16 20:35:35.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:35.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:35.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:35.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed)
Nov 16 20:35:35.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:35.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:35.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:35.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:35.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:35.918: INFO:
Nov 16 20:35:37.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:37.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:37.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:37.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed)
Nov 16 20:35:37.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:37.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:37.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:37.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:37.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:37.919: INFO:
Nov 16 20:35:39.923: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:39.923: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:39.923: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:39.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed)
Nov 16 20:35:39.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:39.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:39.923: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:39.923: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:39.923: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:39.923: INFO:
Nov 16 20:35:41.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:41.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:41.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:41.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed)
Nov 16 20:35:41.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:41.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:41.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:41.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:41.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:41.918: INFO:
Nov 16 20:35:43.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:43.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:43.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:43.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed)
Nov 16 20:35:43.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:43.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:43.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:43.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:43.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:43.918: INFO:
Nov 16 20:35:45.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:45.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:45.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:45.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed)
Nov 16 20:35:45.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:45.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:45.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:45.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:45.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:45.922: INFO:
Nov 16 20:35:48.030: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:48.030: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:48.030: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:48.030: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed)
Nov 16 20:35:48.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:48.030: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:48.030: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:48.030: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:48.030: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:48.030: INFO:
Nov 16 20:35:49.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:49.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:49.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:49.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed)
Nov 16 20:35:49.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:49.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:49.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:49.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:49.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:49.922: INFO:
Nov 16 20:35:51.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:51.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:51.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:51.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed)
Nov 16 20:35:51.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:51.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:51.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:51.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:51.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:51.915: INFO:
Nov 16 20:35:53.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:53.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:53.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:53.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed)
Nov 16 20:35:53.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:53.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:53.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:53.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:53.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:53.919: INFO:
Nov 16 20:35:55.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:55.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:55.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:55.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed)
Nov 16 20:35:55.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:55.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:55.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:55.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:55.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:55.916: INFO:
Nov 16 20:35:57.930: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:57.930: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:57.930: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:57.930: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed)
Nov 16 20:35:57.930: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:57.930: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:57.930: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:57.930: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:57.930: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:57.930: INFO:
Nov 16 20:35:59.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:59.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:59.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:35:59.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed)
Nov 16 20:35:59.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:35:59.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:35:59.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:59.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:59.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:35:59.919: INFO:
Nov 16 20:36:01.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:01.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:01.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:01.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed)
Nov 16 20:36:01.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:01.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:01.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:01.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:01.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:01.919: INFO:
Nov 16 20:36:03.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:03.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:03.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:03.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed)
Nov 16 20:36:03.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:03.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:03.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:03.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:03.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:03.917: INFO:
Nov 16 20:36:05.927: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:05.927: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:05.927: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:05.928: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed)
Nov 16 20:36:05.928: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:05.928: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:05.928: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:05.928: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:05.928: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:05.928: INFO:
Nov 16 20:36:07.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:07.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:07.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:07.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed)
Nov 16 20:36:07.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:07.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:07.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:07.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:07.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:07.919: INFO:
Nov 16 20:36:09.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:09.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:09.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:09.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed)
Nov 16 20:36:09.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:09.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:09.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:09.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:09.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:09.918: INFO:
Nov 16 20:36:11.924: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:11.924: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:11.924: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:11.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed)
Nov 16 20:36:11.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:11.924: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:11.924: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:11.924: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:11.924: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:11.924: INFO:
Nov 16 20:36:13.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:13.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:13.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:13.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed)
Nov 16 20:36:13.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:13.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:13.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:13.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:13.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:13.913: INFO:
Nov 16 20:36:15.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:15.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:15.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:15.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed)
Nov 16 20:36:15.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:15.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:15.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:15.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:15.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:15.922: INFO:
Nov 16 20:36:17.928: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:17.928: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:17.928: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:17.928: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed)
Nov 16 20:36:17.928: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:17.928: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:17.928: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:17.928: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:17.928: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:17.928: INFO:
Nov 16 20:36:19.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:19.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:19.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:19.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed)
Nov 16 20:36:19.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:19.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:19.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:19.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:19.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:19.917: INFO:
Nov 16 20:36:21.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:21.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:21.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:21.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed)
Nov 16 20:36:21.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:21.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:21.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:21.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:21.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:21.920: INFO:
Nov 16 20:36:24.032: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:24.032: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:24.032: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:24.032: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed)
Nov 16 20:36:24.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:24.032: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:24.032: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:24.032: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:24.032: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:24.032: INFO:
Nov 16 20:36:25.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:25.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:25.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:25.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed)
Nov 16 20:36:25.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:25.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:25.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:25.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:25.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:25.922: INFO:
Nov 16 20:36:27.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:27.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:27.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:27.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed)
Nov 16 20:36:27.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:27.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:27.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:27.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:27.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:27.917: INFO:
Nov 16 20:36:29.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:29.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:29.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:29.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed)
Nov 16 20:36:29.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:29.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:29.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:29.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:29.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:29.919: INFO:
Nov 16 20:36:31.924: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:31.924: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:31.924: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:31.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed)
Nov 16 20:36:31.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:31.924: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:31.924: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:31.924: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:31.924: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:31.924: INFO:
Nov 16 20:36:33.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:33.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:33.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:33.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed)
Nov 16 20:36:33.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:33.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:33.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:33.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:33.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:33.915: INFO:
Nov 16 20:36:35.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:35.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:35.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:35.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed)
Nov 16 20:36:35.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:35.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:35.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:35.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:35.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:35.916: INFO:
Nov 16 20:36:37.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:37.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:37.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:37.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed)
Nov 16 20:36:37.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:37.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:37.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:37.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:37.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:37.920: INFO:
Nov 16 20:36:39.927: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:39.927: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:39.927: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:39.927: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed)
Nov 16 20:36:39.927: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:39.927: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:39.927: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:39.927: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:39.927: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:39.927: INFO:
Nov 16 20:36:41.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:41.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:41.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:41.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed)
Nov 16 20:36:41.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:41.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:41.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:41.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:41.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:41.922: INFO:
Nov 16 20:36:43.926: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:43.926: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:43.926: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:43.926: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed)
Nov 16 20:36:43.926: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:43.926: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:43.926: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:43.926: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:43.926: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:43.926: INFO:
Nov 16 20:36:45.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:45.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:45.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:45.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed)
Nov 16 20:36:45.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:45.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:45.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:45.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:45.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:45.917: INFO:
Nov 16 20:36:48.030: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:48.030: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:48.030: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:48.030: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed)
Nov 16 20:36:48.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:48.030: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:48.030: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:48.030: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:48.030: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:48.030: INFO:
Nov 16 20:36:49.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:49.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:49.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:49.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed)
Nov 16 20:36:49.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:49.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:49.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:49.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:49.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:49.922: INFO:
Nov 16 20:36:51.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:51.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:51.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:51.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed)
Nov 16 20:36:51.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:51.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:51.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:51.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:51.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:51.919: INFO:
Nov 16 20:36:53.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:53.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:53.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:53.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed)
Nov 16 20:36:53.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:53.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:53.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:53.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:53.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:53.918: INFO:
Nov 16 20:36:55.925: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:55.925: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:55.925: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:55.925: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed)
Nov 16 20:36:55.925: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:55.925: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:55.925: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:55.925: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:55.925: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:55.925: INFO:
Nov 16 20:36:57.921: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:57.921: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:57.921: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:57.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed)
Nov 16 20:36:57.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:57.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:57.921: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:57.921: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:57.921: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:57.921: INFO:
Nov 16 20:36:59.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:59.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:59.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:36:59.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed)
Nov 16 20:36:59.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:36:59.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:36:59.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:59.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:59.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:36:59.919: INFO:
Nov 16 20:37:01.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:01.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:01.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:01.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed)
Nov 16 20:37:01.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:01.913: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:01.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:01.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:01.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:01.913: INFO:
Nov 16 20:37:03.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:03.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:03.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:03.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed)
Nov 16 20:37:03.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:03.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:03.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:03.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:03.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:03.916: INFO:
Nov 16 20:37:05.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:05.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:05.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:05.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed)
Nov 16 20:37:05.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:05.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:05.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:05.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:05.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:05.916: INFO:
Nov 16 20:37:07.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:07.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:07.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:07.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed)
Nov 16 20:37:07.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:07.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:07.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:07.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:07.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:07.915: INFO:
Nov 16 20:37:09.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:09.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:09.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:09.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed)
Nov 16 20:37:09.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:09.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:09.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:09.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:09.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:09.919: INFO:
Nov 16 20:37:11.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:11.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:11.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:11.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed)
Nov 16 20:37:11.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:11.915: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:11.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:11.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:11.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:11.915: INFO:
Nov 16 20:37:13.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:13.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:13.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:13.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed)
Nov 16 20:37:13.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:13.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:13.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:13.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:13.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:13.916: INFO:
Nov 16 20:37:15.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:15.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:15.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:15.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed)
Nov 16 20:37:15.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:15.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:15.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:15.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:15.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:15.922: INFO:
Nov 16 20:37:17.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:17.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:17.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:17.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed)
Nov 16 20:37:17.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:17.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:17.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:17.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:17.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:17.916: INFO:
Nov 16 20:37:19.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:19.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:19.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:19.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed)
Nov 16 20:37:19.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:19.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:19.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:19.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:19.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:19.920: INFO:
Nov 16 20:37:21.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:21.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:21.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:21.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed)
Nov 16 20:37:21.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:21.919: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:21.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:21.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:21.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:21.919: INFO:
Nov 16 20:37:23.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:23.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:23.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:23.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed)
Nov 16 20:37:23.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:23.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:23.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:23.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:23.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:23.914: INFO:
Nov 16 20:37:25.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:25.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:25.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:25.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed)
Nov 16 20:37:25.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:25.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:25.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:25.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:25.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:25.917: INFO:
Nov 16 20:37:27.921: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:27.921: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:27.921: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:27.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed)
Nov 16 20:37:27.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:27.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:27.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:27.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:27.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:27.922: INFO:
Nov 16 20:37:29.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:29.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:29.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:29.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed)
Nov 16 20:37:29.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:29.914: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:29.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:29.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:29.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:29.914: INFO:
Nov 16 20:37:31.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:31.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:31.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:31.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed)
Nov 16 20:37:31.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:31.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:31.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:31.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:31.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:31.920: INFO:
Nov 16 20:37:33.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:33.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:33.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:33.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed)
Nov 16 20:37:33.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:33.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:33.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:33.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:33.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:33.922: INFO:
Nov 16 20:37:35.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:35.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:35.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:35.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed)
Nov 16 20:37:35.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:35.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:35.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:35.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:35.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:35.918: INFO:
Nov 16 20:37:37.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:37.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:37.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:37.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed)
Nov 16 20:37:37.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:37.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:37.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:37.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:37.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:37.916: INFO:
Nov 16 20:37:39.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:39.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:39.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:39.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed)
Nov 16 20:37:39.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:39.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:39.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:39.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:39.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:39.920: INFO:
Nov 16 20:37:44.007: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:44.007: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:44.007: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:44.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed)
Nov 16 20:37:44.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:44.007: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:44.007: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:44.007: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:44.007: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:44.007: INFO:
Nov 16 20:37:45.923: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:45.923: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:45.923: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:45.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed)
Nov 16 20:37:45.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:45.923: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:45.923: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:45.923: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:45.923: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:45.923: INFO:
Nov 16 20:37:47.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:47.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:47.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:47.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed)
Nov 16 20:37:47.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:47.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:47.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:47.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:47.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:47.916: INFO:
Nov 16 20:37:49.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:49.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:49.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:49.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed)
Nov 16 20:37:49.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:49.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:49.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:49.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:49.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:49.917: INFO:
Nov 16 20:37:51.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:51.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:51.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:51.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed)
Nov 16 20:37:51.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:51.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:51.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:51.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:51.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:51.916: INFO:
Nov 16 20:37:53.933: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:53.933: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:53.933: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:53.933: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed)
Nov 16 20:37:53.933: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:53.933: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:53.933: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:53.933: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:53.933: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:53.933: INFO:
Nov 16 20:37:55.921: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:55.921: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:55.921: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:55.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed)
Nov 16 20:37:55.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:55.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:55.921: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:55.921: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:55.921: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:55.921: INFO:
Nov 16 20:37:57.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:57.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:57.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:57.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed)
Nov 16 20:37:57.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:57.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:57.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:57.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:57.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:57.920: INFO:
Nov 16 20:37:59.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:59.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:59.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:37:59.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed)
Nov 16 20:37:59.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:37:59.920: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:37:59.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:59.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:59.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:37:59.920: INFO:
Nov 16 20:38:01.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:01.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:01.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:01.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed)
Nov 16 20:38:01.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:01.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:01.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:01.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:01.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:01.916: INFO:
Nov 16 20:38:03.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:03.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:03.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:03.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed)
Nov 16 20:38:03.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:03.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:03.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:03.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:03.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:03.918: INFO:
Nov 16 20:38:05.925: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:05.925: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:05.925: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:05.925: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed)
Nov 16 20:38:05.925: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:05.925: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:05.925: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:05.925: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:05.925: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:05.925: INFO:
Nov 16 20:38:07.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:07.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:07.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:07.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed)
Nov 16 20:38:07.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:07.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:07.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:07.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:07.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:07.917: INFO:
Nov 16 20:38:09.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:09.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:09.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:09.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed)
Nov 16 20:38:09.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:09.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:09.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:09.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:09.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:09.918: INFO:
Nov 16 20:38:11.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:11.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:11.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:11.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed)
Nov 16 20:38:11.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:11.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:11.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:11.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:11.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:11.917: INFO:
Nov 16 20:38:13.921: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:13.921: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:13.921: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:13.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed)
Nov 16 20:38:13.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:13.921: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:13.921: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:13.921: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:13.921: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:13.921: INFO:
Nov 16 20:38:15.924: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:15.924: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:15.924: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:15.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed)
Nov 16 20:38:15.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:15.924: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:15.924: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:15.924: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:15.924: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:15.924: INFO:
Nov 16 20:38:17.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:17.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:17.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:17.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed)
Nov 16 20:38:17.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:17.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:17.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:17.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:17.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:17.918: INFO:
Nov 16 20:38:19.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:19.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:19.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:19.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed)
Nov 16 20:38:19.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:19.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:19.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:19.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:19.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:19.916: INFO:
Nov 16 20:38:21.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:21.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:21.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:21.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed)
Nov 16 20:38:21.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:21.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:21.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:21.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:21.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:21.917: INFO:
Nov 16 20:38:23.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:23.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:23.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:23.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed)
Nov 16 20:38:23.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:23.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:23.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:23.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:23.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:23.918: INFO:
Nov 16 20:38:25.924: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:25.924: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:25.924: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:25.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed)
Nov 16 20:38:25.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:25.924: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:25.924: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:25.924: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:25.924: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:25.924: INFO:
Nov 16 20:38:27.931: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:27.931: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:27.931: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:27.931: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed)
Nov 16 20:38:27.931: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:27.931: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:27.931: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:27.931: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:27.931: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:27.931: INFO:
Nov 16 20:38:29.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:29.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:29.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:29.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed)
Nov 16 20:38:29.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:29.916: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:29.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:29.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:29.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:29.916: INFO:
Nov 16 20:38:31.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:31.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:31.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:31.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed)
Nov 16 20:38:31.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:31.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:31.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:31.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:31.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:31.918: INFO:
Nov 16 20:38:33.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:33.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:33.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:33.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed)
Nov 16 20:38:33.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:33.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:33.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:33.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:33.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:33.917: INFO:
Nov 16 20:38:35.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:35.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:35.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:35.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed)
Nov 16 20:38:35.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:35.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:35.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:35.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:35.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:35.917: INFO:
Nov 16 20:38:37.925: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:37.925: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:37.925: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:37.925: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed)
Nov 16 20:38:37.925: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:37.925: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:37.925: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:37.925: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:37.925: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:37.925: INFO:
Nov 16 20:38:39.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:39.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:39.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:39.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (596 seconds elapsed)
Nov 16 20:38:39.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:39.922: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:39.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:39.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:39.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:39.922: INFO:
Nov 16 20:38:41.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:41.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:41.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:41.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (598 seconds elapsed)
Nov 16 20:38:41.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:41.918: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:41.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:41.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:41.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:41.918: INFO:
Nov 16 20:38:43.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:43.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:43.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:43.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 16 20:38:43.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:43.917: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:43.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:43.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:43.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:43.917: INFO:
Nov 16 20:38:44.050: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:44.050: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:44.050: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Nov 16 20:38:44.050: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (600 seconds elapsed)
Nov 16 20:38:44.050: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready.
Nov 16 20:38:44.050: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:44.050: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:44.050: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:44.050: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:44.050: INFO:
�[1mSTEP:�[0m Collecting events from namespace "kube-system". �[38;5;243m11/16/22 20:38:44.05�[0m
�[1mSTEP:�[0m Found 127 events. �[38;5;243m11/16/22 20:38:44.115�[0m
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:23:49 +0000 UTC - event for kube-controller-manager: {kube-controller-manager } LeaderElection: capz-conf-spjmpp-control-plane-kbwv8_a0afebe3-8336-4730-8a72-0e836ce902ce became leader
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:23:51 +0000 UTC - event for kube-scheduler: {default-scheduler } LeaderElection: capz-conf-spjmpp-control-plane-kbwv8_1d1a670d-e9d7-4d3b-a00a-830d5b31e92f became leader
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:23:55 +0000 UTC - event for coredns: {deployment-controller } ScalingReplicaSet: Scaled up replica set coredns-787d4945fb to 2
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:23:55 +0000 UTC - event for kube-proxy: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-x5hpm
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:23:55 +0000 UTC - event for kube-proxy-x5hpm: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-x5hpm to capz-conf-spjmpp-control-plane-kbwv8
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:23:56 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-vrqg5
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:23:56 +0000 UTC - event for coredns-787d4945fb: {replicaset-controller } SuccessfulCreate: Created pod: coredns-787d4945fb-dwzcm
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:23:56 +0000 UTC - event for coredns-787d4945fb-dwzcm: {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 16 20:38:44.116: INFO: At 2022-11-16 20:23:56 +0000 UTC - event for coredns-787d4945fb-vrqg5: {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 16 20:38:44.116: INFO: At 2022-11-16 20:23:57 +0000 UTC - event for kube-proxy-x5hpm: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Pulling: Pulling image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.34_e4fc500f3ca85b"
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:00 +0000 UTC - event for kube-proxy-x5hpm: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Started: Started container kube-proxy
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:00 +0000 UTC - event for kube-proxy-x5hpm: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Created: Created container kube-proxy
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:00 +0000 UTC - event for kube-proxy-x5hpm: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Pulled: Successfully pulled image "capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.34_e4fc500f3ca85b" in 2.9067226s (2.9067448s including waiting)
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:06 +0000 UTC - event for metrics-server: {deployment-controller } ScalingReplicaSet: Scaled up replica set metrics-server-c9574f845 to 1
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:06 +0000 UTC - event for metrics-server-c9574f845: {replicaset-controller } SuccessfulCreate: Created pod: metrics-server-c9574f845-zv6fj
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:06 +0000 UTC - event for metrics-server-c9574f845-zv6fj: {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 16 20:38:44.116: INFO: At 2022-11-16 20:24:08 +0000 UTC - event for calico-kube-controllers: {deployment-controller } ScalingReplicaSet: Scaled up replica set calico-kube-controllers-657b584867 to 1
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:08 +0000 UTC - event for calico-kube-controllers-657b584867: {replicaset-controller } SuccessfulCreate: Created pod: calico-kube-controllers-657b584867-j7n48
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:08 +0000 UTC - event for calico-kube-controllers-657b584867-j7n48: {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 16 20:38:44.116: INFO: At 2022-11-16 20:24:08 +0000 UTC - event for calico-node: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-sqgnc
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:08 +0000 UTC - event for calico-node-sqgnc: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-sqgnc to capz-conf-spjmpp-control-plane-kbwv8
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:09 +0000 UTC - event for calico-node-sqgnc: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Pulling: Pulling image "docker.io/calico/cni:v3.23.0"
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:17 +0000 UTC - event for calico-node-sqgnc: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Pulled: Successfully pulled image "docker.io/calico/cni:v3.23.0" in 8.21865468s (8.21866098s including waiting)
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:17 +0000 UTC - event for calico-node-sqgnc: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Created: Created container upgrade-ipam
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:17 +0000 UTC - event for calico-node-sqgnc: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Started: Started container upgrade-ipam
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:21 +0000 UTC - event for calico-node-sqgnc: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Started: Started container install-cni
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:21 +0000 UTC - event for calico-node-sqgnc: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Pulled: Container image "docker.io/calico/cni:v3.23.0" already present on machine
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:21 +0000 UTC - event for calico-node-sqgnc: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Created: Created container install-cni
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:24 +0000 UTC - event for calico-kube-controllers-657b584867-j7n48: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-kube-controllers-657b584867-j7n48 to capz-conf-spjmpp-control-plane-kbwv8
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:24 +0000 UTC - event for calico-kube-controllers-657b584867-j7n48: {kubelet capz-conf-spjmpp-control-plane-kbwv8} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "9b5b5af8aadea757956c850e24b1436997f3440dd8b0f5dcd4425881c6ae8911": 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 16 20:38:44.116: INFO: At 2022-11-16 20:24:24 +0000 UTC - event for calico-node-sqgnc: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Pulling: Pulling image "docker.io/calico/node:v3.23.0"
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:24 +0000 UTC - event for coredns-787d4945fb-dwzcm: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-dwzcm to capz-conf-spjmpp-control-plane-kbwv8
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:24 +0000 UTC - event for coredns-787d4945fb-vrqg5: {default-scheduler } Scheduled: Successfully assigned kube-system/coredns-787d4945fb-vrqg5 to capz-conf-spjmpp-control-plane-kbwv8
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:24 +0000 UTC - event for metrics-server-c9574f845-zv6fj: {default-scheduler } Scheduled: Successfully assigned kube-system/metrics-server-c9574f845-zv6fj to capz-conf-spjmpp-control-plane-kbwv8
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:25 +0000 UTC - event for coredns-787d4945fb-dwzcm: {kubelet capz-conf-spjmpp-control-plane-kbwv8} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "c72796b11d13d1b3b037ce03cfed56bec165f604bb2c9219ad5a10d79d71ad90": 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 16 20:38:44.116: INFO: At 2022-11-16 20:24:25 +0000 UTC - event for coredns-787d4945fb-vrqg5: {kubelet capz-conf-spjmpp-control-plane-kbwv8} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "4fb351852141b7a86d4873e35bd8696268fb15997c4dd85f37496386618ea74d": 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 16 20:38:44.116: INFO: At 2022-11-16 20:24:25 +0000 UTC - event for metrics-server-c9574f845-zv6fj: {kubelet capz-conf-spjmpp-control-plane-kbwv8} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "eecb4c3e032eca03d72d4c822382d3cc9cef0460c091f83eed0f429d91567aca": 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 16 20:38:44.116: INFO: At 2022-11-16 20:24:33 +0000 UTC - event for calico-node-sqgnc: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Pulled: Successfully pulled image "docker.io/calico/node:v3.23.0" in 9.205440233s (9.205455628s including waiting)
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:33 +0000 UTC - event for calico-node-sqgnc: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Created: Created container calico-node
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:34 +0000 UTC - event for calico-node-sqgnc: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Started: Started container calico-node
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:34 +0000 UTC - event for calico-node-sqgnc: {kubelet capz-conf-spjmpp-control-plane-kbwv8} 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 16 20:38:44.116: INFO: At 2022-11-16 20:24:36 +0000 UTC - event for coredns-787d4945fb-vrqg5: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:36 +0000 UTC - event for coredns-787d4945fb-vrqg5: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Created: Created container coredns
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:37 +0000 UTC - event for coredns-787d4945fb-vrqg5: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Started: Started container coredns
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:37 +0000 UTC - event for coredns-787d4945fb-vrqg5: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Unhealthy: Readiness probe failed: Get "http://192.168.133.1:8181/ready": dial tcp 192.168.133.1:8181: connect: connection refused
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:37 +0000 UTC - event for metrics-server-c9574f845-zv6fj: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Pulling: Pulling image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2"
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:40 +0000 UTC - event for coredns-787d4945fb-dwzcm: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Started: Started container coredns
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:40 +0000 UTC - event for coredns-787d4945fb-dwzcm: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Created: Created container coredns
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:40 +0000 UTC - event for coredns-787d4945fb-dwzcm: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Pulled: Container image "registry.k8s.io/coredns/coredns:v1.9.3" already present on machine
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:41 +0000 UTC - event for calico-kube-controllers-657b584867-j7n48: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Pulling: Pulling image "docker.io/calico/kube-controllers:v3.23.0"
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:44 +0000 UTC - event for metrics-server-c9574f845-zv6fj: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Pulled: Successfully pulled image "k8s.gcr.io/metrics-server/metrics-server:v0.5.2" in 6.257625029s (6.257685426s including waiting)
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:44 +0000 UTC - event for metrics-server-c9574f845-zv6fj: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Created: Created container metrics-server
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:44 +0000 UTC - event for metrics-server-c9574f845-zv6fj: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Started: Started container metrics-server
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:50 +0000 UTC - event for calico-kube-controllers-657b584867-j7n48: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Pulled: Successfully pulled image "docker.io/calico/kube-controllers:v3.23.0" in 6.390495503s (9.050577995s including waiting)
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:50 +0000 UTC - event for calico-kube-controllers-657b584867-j7n48: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Created: Created container calico-kube-controllers
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:24:50 +0000 UTC - event for calico-kube-controllers-657b584867-j7n48: {kubelet capz-conf-spjmpp-control-plane-kbwv8} Started: Started container calico-kube-controllers
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:29 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-rqv4b
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:29 +0000 UTC - event for calico-node-windows: {daemonset-controller } SuccessfulCreate: Created pod: calico-node-windows-fl2zr
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:29 +0000 UTC - event for calico-node-windows-fl2zr: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-fl2zr to capz-conf-x9q7m
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:29 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-v76zv
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:29 +0000 UTC - event for containerd-logger-v76zv: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-v76zv to capz-conf-x9q7m
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:29 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-kx97p
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:29 +0000 UTC - event for kube-proxy-windows-kx97p: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-kx97p to capz-conf-x9q7m
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:30 +0000 UTC - event for calico-node-windows-rqv4b: {default-scheduler } Scheduled: Successfully assigned kube-system/calico-node-windows-rqv4b to capz-conf-mq8ck
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:30 +0000 UTC - event for containerd-logger: {daemonset-controller } SuccessfulCreate: Created pod: containerd-logger-vwt8f
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:30 +0000 UTC - event for containerd-logger-vwt8f: {default-scheduler } Scheduled: Successfully assigned kube-system/containerd-logger-vwt8f to capz-conf-mq8ck
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:30 +0000 UTC - event for kube-proxy-windows: {daemonset-controller } SuccessfulCreate: Created pod: kube-proxy-windows-lgx8s
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:30 +0000 UTC - event for kube-proxy-windows-lgx8s: {default-scheduler } Scheduled: Successfully assigned kube-system/kube-proxy-windows-lgx8s to capz-conf-mq8ck
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:31 +0000 UTC - event for calico-node-windows-fl2zr: {kubelet capz-conf-x9q7m} FailedMount: MountVolume.SetUp failed for volume "kubeadm-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:31 +0000 UTC - event for calico-node-windows-rqv4b: {kubelet capz-conf-mq8ck} FailedMount: MountVolume.SetUp failed for volume "kubeadm-config" : failed to sync configmap cache: timed out waiting for the condition
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:31 +0000 UTC - event for kube-proxy-windows-kx97p: {kubelet capz-conf-x9q7m} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:31 +0000 UTC - event for kube-proxy-windows-lgx8s: {kubelet capz-conf-mq8ck} FailedMount: MountVolume.SetUp failed for volume "kube-proxy" : failed to sync configmap cache: timed out waiting for the condition
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:33 +0000 UTC - event for calico-node-windows-rqv4b: {kubelet capz-conf-mq8ck} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unavailable desc = error reading from server: EOF
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:33 +0000 UTC - event for containerd-logger-vwt8f: {kubelet capz-conf-mq8ck} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing open //./pipe/containerd-containerd: The system cannot find the file specified."
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:33 +0000 UTC - event for kube-proxy-windows-lgx8s: {kubelet capz-conf-mq8ck} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unavailable desc = error reading from server: EOF
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:47 +0000 UTC - event for calico-node-windows-fl2zr: {kubelet capz-conf-x9q7m} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:47 +0000 UTC - event for containerd-logger-v76zv: {kubelet capz-conf-x9q7m} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:47 +0000 UTC - event for kube-proxy-windows-kx97p: {kubelet capz-conf-x9q7m} Started: Started container kube-proxy
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:47 +0000 UTC - event for kube-proxy-windows-kx97p: {kubelet capz-conf-x9q7m} Pulled: Container image "sigwindowstools/kube-proxy:v1.27.0-alpha.0.26_43b7a253539a77-calico-hostprocess" already present on machine
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:47 +0000 UTC - event for kube-proxy-windows-kx97p: {kubelet capz-conf-x9q7m} Created: Created container kube-proxy
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:53 +0000 UTC - event for calico-node-windows-fl2zr: {kubelet capz-conf-x9q7m} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 6.096121s (6.096121s including waiting)
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:53 +0000 UTC - event for calico-node-windows-fl2zr: {kubelet capz-conf-x9q7m} Started: Started container install-cni
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:53 +0000 UTC - event for calico-node-windows-fl2zr: {kubelet capz-conf-x9q7m} Created: Created container install-cni
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:55 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-chgxz
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:56 +0000 UTC - event for containerd-logger-v76zv: {kubelet capz-conf-x9q7m} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 3.8879326s (9.9595135s including waiting)
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:56 +0000 UTC - event for csi-proxy-chgxz: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-chgxz to capz-conf-x9q7m
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:57 +0000 UTC - event for csi-proxy-chgxz: {kubelet capz-conf-x9q7m} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:27:58 +0000 UTC - event for calico-node-windows-fl2zr: {kubelet capz-conf-x9q7m} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:04 +0000 UTC - event for containerd-logger-v76zv: {kubelet capz-conf-x9q7m} Started: Started container containerd-logger
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:04 +0000 UTC - event for containerd-logger-v76zv: {kubelet capz-conf-x9q7m} Created: Created container containerd-logger
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:07 +0000 UTC - event for calico-node-windows-rqv4b: {kubelet capz-conf-mq8ck} Pulling: Pulling image "sigwindowstools/calico-install:v3.23.0-hostprocess"
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:07 +0000 UTC - event for containerd-logger-vwt8f: {kubelet capz-conf-mq8ck} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0"
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:07 +0000 UTC - event for kube-proxy-windows-lgx8s: {kubelet capz-conf-mq8ck} Created: Created container kube-proxy
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:07 +0000 UTC - event for kube-proxy-windows-lgx8s: {kubelet capz-conf-mq8ck} Pulled: Container image "sigwindowstools/kube-proxy:v1.27.0-alpha.0.26_43b7a253539a77-calico-hostprocess" already present on machine
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:08 +0000 UTC - event for kube-proxy-windows-lgx8s: {kubelet capz-conf-mq8ck} Started: Started container kube-proxy
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:11 +0000 UTC - event for containerd-logger-vwt8f: {kubelet capz-conf-mq8ck} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/eventflow-logger:v0.1.0" in 3.4985448s (3.4985448s including waiting)
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:12 +0000 UTC - event for csi-proxy-chgxz: {kubelet capz-conf-x9q7m} Created: Created container csi-proxy
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:12 +0000 UTC - event for csi-proxy-chgxz: {kubelet capz-conf-x9q7m} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 15.5941395s (15.5941395s including waiting)
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:13 +0000 UTC - event for csi-proxy-chgxz: {kubelet capz-conf-x9q7m} Started: Started container csi-proxy
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:16 +0000 UTC - event for calico-node-windows-rqv4b: {kubelet capz-conf-mq8ck} Created: Created container install-cni
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:16 +0000 UTC - event for calico-node-windows-rqv4b: {kubelet capz-conf-mq8ck} Pulled: Successfully pulled image "sigwindowstools/calico-install:v3.23.0-hostprocess" in 5.2876009s (8.7816742s including waiting)
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:16 +0000 UTC - event for calico-node-windows-rqv4b: {kubelet capz-conf-mq8ck} Started: Started container install-cni
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:16 +0000 UTC - event for containerd-logger-vwt8f: {kubelet capz-conf-mq8ck} Created: Created container containerd-logger
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:16 +0000 UTC - event for containerd-logger-vwt8f: {kubelet capz-conf-mq8ck} Started: Started container containerd-logger
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:18 +0000 UTC - event for calico-node-windows-fl2zr: {kubelet capz-conf-x9q7m} Started: Started container calico-node-startup
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:18 +0000 UTC - event for calico-node-windows-fl2zr: {kubelet capz-conf-x9q7m} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:18 +0000 UTC - event for calico-node-windows-fl2zr: {kubelet capz-conf-x9q7m} Created: Created container calico-node-startup
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:18 +0000 UTC - event for calico-node-windows-fl2zr: {kubelet capz-conf-x9q7m} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 5.6178789s (19.8664371s including waiting)
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:18 +0000 UTC - event for csi-proxy: {daemonset-controller } SuccessfulCreate: Created pod: csi-proxy-jdc8p
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:18 +0000 UTC - event for csi-proxy-jdc8p: {default-scheduler } Scheduled: Successfully assigned kube-system/csi-proxy-jdc8p to capz-conf-mq8ck
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:19 +0000 UTC - event for calico-node-windows-fl2zr: {kubelet capz-conf-x9q7m} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 890.0362ms (890.0362ms including waiting)
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:19 +0000 UTC - event for csi-proxy-jdc8p: {kubelet capz-conf-mq8ck} Pulling: Pulling image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2"
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:22 +0000 UTC - event for calico-node-windows-rqv4b: {kubelet capz-conf-mq8ck} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:25 +0000 UTC - event for calico-node-windows-fl2zr: {kubelet capz-conf-x9q7m} Created: Created container calico-node-felix
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:25 +0000 UTC - event for calico-node-windows-fl2zr: {kubelet capz-conf-x9q7m} Started: Started container calico-node-felix
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:32 +0000 UTC - event for csi-proxy-jdc8p: {kubelet capz-conf-mq8ck} Pulled: Successfully pulled image "ghcr.io/kubernetes-sigs/sig-windows/csi-proxy:v1.0.2" in 12.6445532s (12.6445532s including waiting)
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:32 +0000 UTC - event for csi-proxy-jdc8p: {kubelet capz-conf-mq8ck} Created: Created container csi-proxy
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:32 +0000 UTC - event for csi-proxy-jdc8p: {kubelet capz-conf-mq8ck} Started: Started container csi-proxy
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:37 +0000 UTC - event for calico-node-windows-rqv4b: {kubelet capz-conf-mq8ck} Pulling: Pulling image "sigwindowstools/calico-node:v3.23.0-hostprocess"
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:37 +0000 UTC - event for calico-node-windows-rqv4b: {kubelet capz-conf-mq8ck} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 5.2599603s (14.8753168s including waiting)
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:37 +0000 UTC - event for calico-node-windows-rqv4b: {kubelet capz-conf-mq8ck} Created: Created container calico-node-startup
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:37 +0000 UTC - event for calico-node-windows-rqv4b: {kubelet capz-conf-mq8ck} Started: Started container calico-node-startup
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:38 +0000 UTC - event for calico-node-windows-rqv4b: {kubelet capz-conf-mq8ck} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 966.5955ms (966.5955ms including waiting)
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:43 +0000 UTC - event for calico-node-windows-rqv4b: {kubelet capz-conf-mq8ck} Created: Created container calico-node-felix
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:43 +0000 UTC - event for calico-node-windows-rqv4b: {kubelet capz-conf-mq8ck} Started: Started container calico-node-felix
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:28:51 +0000 UTC - event for calico-node-windows-fl2zr: {kubelet capz-conf-x9q7m} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 805.0511ms (805.0511ms including waiting)
Nov 16 20:38:44.116: INFO: At 2022-11-16 20:29:09 +0000 UTC - event for calico-node-windows-rqv4b: {kubelet capz-conf-mq8ck} Pulled: Successfully pulled image "sigwindowstools/calico-node:v3.23.0-hostprocess" in 860.2026ms (860.7333ms including waiting)
Nov 16 20:38:44.173: INFO: POD NODE PHASE GRACE CONDITIONS
Nov 16 20:38:44.173: INFO: calico-kube-controllers-657b584867-j7n48 capz-conf-spjmpp-control-plane-kbwv8 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:24 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:51 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:51 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:24 +0000 UTC }]
Nov 16 20:38:44.173: INFO: calico-node-sqgnc capz-conf-spjmpp-control-plane-kbwv8 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:24 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:39 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:39 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:08 +0000 UTC }]
Nov 16 20:38:44.173: INFO: calico-node-windows-fl2zr capz-conf-x9q7m Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:58 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:58 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:58 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }]
Nov 16 20:38:44.173: INFO: calico-node-windows-rqv4b capz-conf-mq8ck Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:22 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:29:14 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:29:14 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }]
Nov 16 20:38:44.173: INFO: containerd-logger-v76zv capz-conf-x9q7m Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:05 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:05 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }]
Nov 16 20:38:44.173: INFO: containerd-logger-vwt8f capz-conf-mq8ck Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:30 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:17 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:17 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }]
Nov 16 20:38:44.173: INFO: coredns-787d4945fb-dwzcm capz-conf-spjmpp-control-plane-kbwv8 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:24 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:41 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:41 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:24 +0000 UTC }]
Nov 16 20:38:44.173: INFO: coredns-787d4945fb-vrqg5 capz-conf-spjmpp-control-plane-kbwv8 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:24 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:45 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:45 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:24 +0000 UTC }]
Nov 16 20:38:44.173: INFO: csi-proxy-chgxz capz-conf-x9q7m Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:56 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:13 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:13 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:55 +0000 UTC }]
Nov 16 20:38:44.173: INFO: csi-proxy-jdc8p capz-conf-mq8ck Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:18 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:32 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:32 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:18 +0000 UTC }]
Nov 16 20:38:44.173: INFO: etcd-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:23:54 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:23:56 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:23:56 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:23:54 +0000 UTC }]
Nov 16 20:38:44.173: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:44.173: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:44.173: INFO: kube-proxy-windows-kx97p capz-conf-x9q7m Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:48 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:48 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }]
Nov 16 20:38:44.173: INFO: kube-proxy-windows-lgx8s capz-conf-mq8ck Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:30 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:08 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:08 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:30 +0000 UTC }]
Nov 16 20:38:44.173: INFO: kube-proxy-x5hpm capz-conf-spjmpp-control-plane-kbwv8 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:23:55 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:01 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:01 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:23:55 +0000 UTC }]
Nov 16 20:38:44.174: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Nov 16 20:38:44.174: INFO: metrics-server-c9574f845-zv6fj capz-conf-spjmpp-control-plane-kbwv8 Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:24 +0000 UTC } {Ready True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:25:05 +0000 UTC } {ContainersReady True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:25:05 +0000 UTC } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:24:24 +0000 UTC }]
Nov 16 20:38:44.174: INFO:
Nov 16 20:38:44.685: INFO:
Logging node info for node capz-conf-mq8ck
Nov 16 20:38:44.825: INFO: Node Info: &Node{ObjectMeta:{capz-conf-mq8ck dba8f716-9765-4a01-b0e1-d12398e8da2a 1665 0 2022-11-16 20:27:29 +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-mq8ck 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-spjmpp cluster.x-k8s.io/cluster-namespace:capz-conf-spjmpp cluster.x-k8s.io/machine:capz-conf-spjmpp-md-win-67dbc9c465-xpfrt cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-spjmpp-md-win-67dbc9c465 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.20.129 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:ba:d6:76 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet.exe Update v1 2022-11-16 20:27:29 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{".":{},"f:volumes.kubernetes.io/controller-managed-attach-detach":{}},"f:labels":{".":{},"f:beta.kubernetes.io/arch":{},"f:beta.kubernetes.io/instance-type":{},"f:beta.kubernetes.io/os":{},"f:failure-domain.beta.kubernetes.io/region":{},"f:failure-domain.beta.kubernetes.io/zone":{},"f:kubernetes.io/arch":{},"f:kubernetes.io/hostname":{},"f:kubernetes.io/os":{},"f:node.kubernetes.io/instance-type":{},"f:node.kubernetes.io/windows-build":{},"f:topology.kubernetes.io/region":{},"f:topology.kubernetes.io/zone":{}}},"f:spec":{"f:providerID":{}}} } {kubeadm Update v1 2022-11-16 20:27:30 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kube-controller-manager Update v1 2022-11-16 20:28:18 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-16 20:28:35 +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-16 20:29:06 +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-16 20:34:07 +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":{},"f:nodeInfo":{"f:containerRuntimeVersion":{}}}} status}]},Spec:NodeSpec{PodCIDR:,DoNotUseExternalID:,ProviderID:azure:///subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/capz-conf-spjmpp/providers/Microsoft.Compute/virtualMachines/capz-conf-mq8ck,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-16 20:34:07 +0000 UTC,LastTransitionTime:2022-11-16 20:27:29 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-16 20:34:07 +0000 UTC,LastTransitionTime:2022-11-16 20:27:29 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-16 20:34:07 +0000 UTC,LastTransitionTime:2022-11-16 20:27:29 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-16 20:34:07 +0000 UTC,LastTransitionTime:2022-11-16 20:28:18 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-mq8ck,},NodeAddress{Type:InternalIP,Address:10.1.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-mq8ck,SystemUUID:6CFC17A7-9C72-4A55-A7A9-BC80EE977078,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.27.0-alpha.0.34+e4fc500f3ca85b-dirty,KubeProxyVersion:v1.27.0-alpha.0.34+e4fc500f3ca85b-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.27.0-alpha.0.26_43b7a253539a77-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 16 20:38:44.826: INFO:
Logging kubelet events for node capz-conf-mq8ck
Nov 16 20:38:45.026: INFO:
Logging pods the kubelet thinks is on node capz-conf-mq8ck
Nov 16 20:38:45.249: INFO: containerd-logger-vwt8f started at 2022-11-16 20:27:30 +0000 UTC (0+1 container statuses recorded)
Nov 16 20:38:45.249: INFO: Container containerd-logger ready: true, restart count 0
Nov 16 20:38:45.249: INFO: calico-node-windows-rqv4b started at 2022-11-16 20:27:30 +0000 UTC (1+2 container statuses recorded)
Nov 16 20:38:45.249: INFO: Init container install-cni ready: true, restart count 0
Nov 16 20:38:45.249: INFO: Container calico-node-felix ready: true, restart count 1
Nov 16 20:38:45.249: INFO: Container calico-node-startup ready: true, restart count 0
Nov 16 20:38:45.249: INFO: kube-proxy-windows-lgx8s started at 2022-11-16 20:27:30 +0000 UTC (0+1 container statuses recorded)
Nov 16 20:38:45.249: INFO: Container kube-proxy ready: true, restart count 0
Nov 16 20:38:45.249: INFO: csi-proxy-jdc8p started at 2022-11-16 20:28:18 +0000 UTC (0+1 container statuses recorded)
Nov 16 20:38:45.249: INFO: Container csi-proxy ready: true, restart count 0
Nov 16 20:38:45.877: INFO:
Latency metrics for node capz-conf-mq8ck
Nov 16 20:38:45.877: INFO:
Logging node info for node capz-conf-spjmpp-control-plane-kbwv8
Nov 16 20:38:46.026: INFO: Node Info: &Node{ObjectMeta:{capz-conf-spjmpp-control-plane-kbwv8 bac1f489-3146-4251-aa8d-52c3c40494a4 1755 0 2022-11-16 20:23:51 +0000 UTC <nil> <nil> map[beta.kubernetes.io/arch:amd64 beta.kubernetes.io/instance-type:Standard_D2s_v3 beta.kubernetes.io/os:linux failure-domain.beta.kubernetes.io/region:canadacentral failure-domain.beta.kubernetes.io/zone:canadacentral-2 kubernetes.io/arch:amd64 kubernetes.io/hostname:capz-conf-spjmpp-control-plane-kbwv8 kubernetes.io/os:linux node-role.kubernetes.io/control-plane: node.kubernetes.io/exclude-from-external-load-balancers: node.kubernetes.io/instance-type:Standard_D2s_v3 topology.kubernetes.io/region:canadacentral topology.kubernetes.io/zone:canadacentral-2] map[cluster.x-k8s.io/cluster-name:capz-conf-spjmpp cluster.x-k8s.io/cluster-namespace:capz-conf-spjmpp cluster.x-k8s.io/machine:capz-conf-spjmpp-control-plane-gcwl8 cluster.x-k8s.io/owner-kind:KubeadmControlPlane cluster.x-k8s.io/owner-name:capz-conf-spjmpp-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.133.0 volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubelet Update v1 2022-11-16 20:23:51 +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-16 20:23:52 +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-16 20:24:04 +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-16 20:24:24 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}},"f:spec":{"f:taints":{}}} } {Go-http-client Update v1 2022-11-16 20:24:34 +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-16 20:35:07 +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/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/capz-conf-spjmpp/providers/Microsoft.Compute/virtualMachines/capz-conf-spjmpp-control-plane-kbwv8,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-16 20:24:34 +0000 UTC,LastTransitionTime:2022-11-16 20:24:34 +0000 UTC,Reason:CalicoIsUp,Message:Calico is running on this node,},NodeCondition{Type:MemoryPressure,Status:False,LastHeartbeatTime:2022-11-16 20:35:07 +0000 UTC,LastTransitionTime:2022-11-16 20:23:29 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-16 20:35:07 +0000 UTC,LastTransitionTime:2022-11-16 20:23:29 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-16 20:35:07 +0000 UTC,LastTransitionTime:2022-11-16 20:23:29 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-16 20:35:07 +0000 UTC,LastTransitionTime:2022-11-16 20:24:23 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status. AppArmor enabled,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-spjmpp-control-plane-kbwv8,},NodeAddress{Type:InternalIP,Address:10.0.0.4,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:1d31343c657e4f5d93a7c2debc2a3785,SystemUUID:a34a90c3-ed83-cd44-aa36-681ec952d7f8,BootID:576d5890-ee51-4ddd-89e0-2869af61308c,KernelVersion:5.4.0-1091-azure,OSImage:Ubuntu 18.04.6 LTS,ContainerRuntimeVersion:containerd://1.6.2,KubeletVersion:v1.27.0-alpha.0.34+e4fc500f3ca85b,KubeProxyVersion:v1.27.0-alpha.0.34+e4fc500f3ca85b,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:121af24be2bbd325170ee9ba17a300cb00ee46d3b9656034936d00399a802a4e gcr.io/k8s-staging-ci-images/kube-apiserver:v1.27.0-alpha.0.26_43b7a253539a77],SizeBytes:35316643,},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:e5f0cf8e020694b99cca7eb35f1dada09001d9c169249c0ba346608c39712ed2 gcr.io/k8s-staging-ci-images/kube-controller-manager:v1.27.0-alpha.0.26_43b7a253539a77],SizeBytes:32243485,},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:[capzci.azurecr.io/kube-proxy@sha256:c9e48380c3c14d2781f62b1d4fdb1fac826e465954592b72f225e4719d401874 capzci.azurecr.io/kube-proxy:v1.27.0-alpha.0.34_e4fc500f3ca85b],SizeBytes:21542579,},ContainerImage{Names:[gcr.io/k8s-staging-ci-images/kube-proxy@sha256:509f80a3398f317c96af4e9fd66bba992554acf511fe6bd718e6ba9c65a1a033 gcr.io/k8s-staging-ci-images/kube-proxy:v1.27.0-alpha.0.26_43b7a253539a77],SizeBytes:21534346,},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:6219922a29ac1d45ef50f44d0191c8cec697ad5865172b50d08ab949bfb9db30 gcr.io/k8s-staging-ci-images/kube-scheduler:v1.27.0-alpha.0.26_43b7a253539a77],SizeBytes:17482404,},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:7031c1b283388d2c2e09b57badb803c05ebed362dc88d84b480cc47f72a21097 registry.k8s.io/pause:3.9],SizeBytes:321520,},ContainerImage{Names:[registry.k8s.io/pause@sha256:9001185023633d17a2f98ff69b6ff2615b8ea02a825adffa40422f51dfdcde9d registry.k8s.io/pause:3.8],SizeBytes:311286,},ContainerImage{Names:[k8s.gcr.io/pause@sha256:3d380ca8864549e74af4b29c10f9cb0956236dfb01c40ca076fb6c37253234db k8s.gcr.io/pause:3.6],SizeBytes:301773,},},VolumesInUse:[],VolumesAttached:[]AttachedVolume{},Config:nil,},}
Nov 16 20:38:46.027: INFO:
Logging kubelet events for node capz-conf-spjmpp-control-plane-kbwv8
Nov 16 20:38:46.261: INFO:
Logging pods the kubelet thinks is on node capz-conf-spjmpp-control-plane-kbwv8
Nov 16 20:38:46.468: INFO: etcd-capz-conf-spjmpp-control-plane-kbwv8 started at 2022-11-16 20:23:54 +0000 UTC (0+1 container statuses recorded)
Nov 16 20:38:46.468: INFO: Container etcd ready: true, restart count 0
Nov 16 20:38:46.468: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 started at <nil> (0+0 container statuses recorded)
Nov 16 20:38:46.468: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 started at <nil> (0+0 container statuses recorded)
Nov 16 20:38:46.468: INFO: kube-proxy-x5hpm started at 2022-11-16 20:23:55 +0000 UTC (0+1 container statuses recorded)
Nov 16 20:38:46.468: INFO: Container kube-proxy ready: true, restart count 0
Nov 16 20:38:46.468: INFO: coredns-787d4945fb-dwzcm started at 2022-11-16 20:24:24 +0000 UTC (0+1 container statuses recorded)
Nov 16 20:38:46.468: INFO: Container coredns ready: true, restart count 0
Nov 16 20:38:46.468: INFO: coredns-787d4945fb-vrqg5 started at 2022-11-16 20:24:24 +0000 UTC (0+1 container statuses recorded)
Nov 16 20:38:46.468: INFO: Container coredns ready: true, restart count 0
Nov 16 20:38:46.468: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 started at <nil> (0+0 container statuses recorded)
Nov 16 20:38:46.468: INFO: calico-node-sqgnc started at 2022-11-16 20:24:08 +0000 UTC (2+1 container statuses recorded)
Nov 16 20:38:46.468: INFO: Init container upgrade-ipam ready: true, restart count 0
Nov 16 20:38:46.468: INFO: Init container install-cni ready: true, restart count 0
Nov 16 20:38:46.468: INFO: Container calico-node ready: true, restart count 0
Nov 16 20:38:46.468: INFO: metrics-server-c9574f845-zv6fj started at 2022-11-16 20:24:24 +0000 UTC (0+1 container statuses recorded)
Nov 16 20:38:46.468: INFO: Container metrics-server ready: true, restart count 0
Nov 16 20:38:46.468: INFO: calico-kube-controllers-657b584867-j7n48 started at 2022-11-16 20:24:24 +0000 UTC (0+1 container statuses recorded)
Nov 16 20:38:46.468: INFO: Container calico-kube-controllers ready: true, restart count 0
Nov 16 20:38:47.102: INFO:
Latency metrics for node capz-conf-spjmpp-control-plane-kbwv8
Nov 16 20:38:47.102: INFO:
Logging node info for node capz-conf-x9q7m
Nov 16 20:38:47.222: INFO: Node Info: &Node{ObjectMeta:{capz-conf-x9q7m 8710912d-1951-49ef-b6ab-8b93a1df191c 1633 0 2022-11-16 20:27:29 +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-x9q7m 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-spjmpp cluster.x-k8s.io/cluster-namespace:capz-conf-spjmpp cluster.x-k8s.io/machine:capz-conf-spjmpp-md-win-67dbc9c465-pf947 cluster.x-k8s.io/owner-kind:MachineSet cluster.x-k8s.io/owner-name:capz-conf-spjmpp-md-win-67dbc9c465 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.82.1 projectcalico.org/VXLANTunnelMACAddr:00:15:5d:94:74:cd volumes.kubernetes.io/controller-managed-attach-detach:true] [] [] [{kubeadm Update v1 2022-11-16 20:27:29 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:kubeadm.alpha.kubernetes.io/cri-socket":{}}}} } {kubelet.exe Update v1 2022-11-16 20:27:29 +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-16 20:27:55 +0000 UTC FieldsV1 {"f:metadata":{"f:annotations":{"f:node.alpha.kubernetes.io/ttl":{}}}} } {manager Update v1 2022-11-16 20:28:36 +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-16 20:28:48 +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-16 20:33:46 +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/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/capz-conf-spjmpp/providers/Microsoft.Compute/virtualMachines/capz-conf-x9q7m,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-16 20:33:46 +0000 UTC,LastTransitionTime:2022-11-16 20:27:29 +0000 UTC,Reason:KubeletHasSufficientMemory,Message:kubelet has sufficient memory available,},NodeCondition{Type:DiskPressure,Status:False,LastHeartbeatTime:2022-11-16 20:33:46 +0000 UTC,LastTransitionTime:2022-11-16 20:27:29 +0000 UTC,Reason:KubeletHasNoDiskPressure,Message:kubelet has no disk pressure,},NodeCondition{Type:PIDPressure,Status:False,LastHeartbeatTime:2022-11-16 20:33:46 +0000 UTC,LastTransitionTime:2022-11-16 20:27:29 +0000 UTC,Reason:KubeletHasSufficientPID,Message:kubelet has sufficient PID available,},NodeCondition{Type:Ready,Status:True,LastHeartbeatTime:2022-11-16 20:33:46 +0000 UTC,LastTransitionTime:2022-11-16 20:27:55 +0000 UTC,Reason:KubeletReady,Message:kubelet is posting ready status,},},Addresses:[]NodeAddress{NodeAddress{Type:Hostname,Address:capz-conf-x9q7m,},NodeAddress{Type:InternalIP,Address:10.1.0.5,},},DaemonEndpoints:NodeDaemonEndpoints{KubeletEndpoint:DaemonEndpoint{Port:10250,},},NodeInfo:NodeSystemInfo{MachineID:capz-conf-x9q7m,SystemUUID:7A943FEE-F396-4FC5-B817-522933FA07E9,BootID:9,KernelVersion:10.0.17763.3406,OSImage:Windows Server 2019 Datacenter,ContainerRuntimeVersion:containerd://1.6.8,KubeletVersion:v1.27.0-alpha.0.34+e4fc500f3ca85b-dirty,KubeProxyVersion:v1.27.0-alpha.0.34+e4fc500f3ca85b-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.27.0-alpha.0.26_43b7a253539a77-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 16 20:38:47.223: INFO:
Logging kubelet events for node capz-conf-x9q7m
Nov 16 20:38:47.422: INFO:
Logging pods the kubelet thinks is on node capz-conf-x9q7m
Nov 16 20:38:47.629: INFO: containerd-logger-v76zv started at 2022-11-16 20:27:29 +0000 UTC (0+1 container statuses recorded)
Nov 16 20:38:47.629: INFO: Container containerd-logger ready: true, restart count 0
Nov 16 20:38:47.629: INFO: calico-node-windows-fl2zr started at 2022-11-16 20:27:29 +0000 UTC (1+2 container statuses recorded)
Nov 16 20:38:47.629: INFO: Init container install-cni ready: true, restart count 0
Nov 16 20:38:47.629: INFO: Container calico-node-felix ready: true, restart count 1
Nov 16 20:38:47.629: INFO: Container calico-node-startup ready: true, restart count 0
Nov 16 20:38:47.629: INFO: kube-proxy-windows-kx97p started at 2022-11-16 20:27:29 +0000 UTC (0+1 container statuses recorded)
Nov 16 20:38:47.629: INFO: Container kube-proxy ready: true, restart count 0
Nov 16 20:38:47.629: INFO: csi-proxy-chgxz started at 2022-11-16 20:27:56 +0000 UTC (0+1 container statuses recorded)
Nov 16 20:38:47.629: INFO: Container csi-proxy ready: true, restart count 0
Nov 16 20:38:48.284: INFO:
Latency metrics for node capz-conf-x9q7m
Nov 16 20:38:48.440: INFO: Running kubectl logs on non-ready containers in kube-system
Nov 16 20:38:48.822: INFO: Failed to get logs of pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8, container kube-apiserver, err: the server rejected our request for an unknown reason (get pods kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8)
Nov 16 20:38:48.822: INFO: Logs of kube-system/kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8:kube-apiserver on node capz-conf-spjmpp-control-plane-kbwv8
Nov 16 20:38:48.822: INFO: : STARTLOG
ENDLOG for container kube-system:kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8:kube-apiserver
Nov 16 20:38:49.226: INFO: Failed to get logs of pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8, container kube-controller-manager, err: the server rejected our request for an unknown reason (get pods kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8)
Nov 16 20:38:49.226: INFO: Logs of kube-system/kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8:kube-controller-manager on node capz-conf-spjmpp-control-plane-kbwv8
Nov 16 20:38:49.226: INFO: : STARTLOG
ENDLOG for container kube-system:kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8:kube-controller-manager
Nov 16 20:38:49.622: INFO: Failed to get logs of pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8, container kube-scheduler, err: the server rejected our request for an unknown reason (get pods kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8)
Nov 16 20:38:49.622: INFO: Logs of kube-system/kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8:kube-scheduler on node capz-conf-spjmpp-control-plane-kbwv8
Nov 16 20:38:49.622: INFO: : STARTLOG
ENDLOG for container kube-system:kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8:kube-scheduler
Nov 16 20:38:49.622: 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-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
Full Stack Trace
k8s.io/kubernetes/test/e2e.setupSuite()
test/e2e/e2e.go:249 +0x4de
k8s.io/kubernetes/test/e2e.glob..func1()
test/e2e/e2e.go:81 +0x8f
reflect.Value.call({0x66afe40?, 0x789c7c8?, 0x13?}, {0x75bda94, 0x4}, {0xc0000b5f20, 0x0, 0x0?})
/usr/local/go/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0x66afe40?, 0x789c7c8?, 0x26ce5ed?}, {0xc0000a2720?, 0x265cb67?, 0xc0000a2720?})
/usr/local/go/src/reflect/value.go:368 +0xbc
�[38;5;243m<< End Captured GinkgoWriter Output�[0m
�[38;5;9mNov 16 20:38:49.622: 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-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending []
kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 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.197 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.256 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.231 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 7073 Specs in 606.305 seconds�[0m
�[38;5;9m�[1mFAIL!�[0m -- �[38;5;14m�[1mA BeforeSuite node failed so all tests were skipped.�[0m
I1116 20:28:43.076379 14 e2e.go:126] Starting e2e run "b35881a8-9fbe-4fc1-8737-9643502e4194" 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.66s)
FAIL
I1116 20:28:43.078210 15 e2e.go:126] Starting e2e run "ae1c05b5-0042-43e8-a125-8a55f8b9c8b9" 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.60s)
FAIL
I1116 20:28:43.097484 17 e2e.go:126] Starting e2e run "3bc4bfbf-b5ab-42de-a52e-7d3a8df55b65" 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.57s)
FAIL
I1116 20:28:43.076127 19 e2e.go:126] Starting e2e run "33542e16-5166-49ca-a1c6-3db119679b06" 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.60s)
FAIL
Ginkgo ran 1 suite in 10m6.828473609s
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 16 20:38:50.186: INFO: FAILED!
Nov 16 20:38:50.186: INFO: Cleaning up after "Conformance Tests conformance-tests" spec
�[1mSTEP�[0m: Dumping logs from the "capz-conf-spjmpp" workload cluster
�[1mSTEP�[0m: Dumping workload cluster capz-conf-spjmpp/capz-conf-spjmpp logs
Nov 16 20:38:50.276: INFO: Collecting logs for Linux node capz-conf-spjmpp-control-plane-kbwv8 in cluster capz-conf-spjmpp in namespace capz-conf-spjmpp
Nov 16 20:39:12.529: INFO: Collecting boot logs for AzureMachine capz-conf-spjmpp-control-plane-kbwv8
Nov 16 20:39:13.510: INFO: Collecting logs for Windows node capz-conf-x9q7m in cluster capz-conf-spjmpp in namespace capz-conf-spjmpp
Nov 16 20:41:40.900: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-x9q7m to /logs/artifacts/clusters/capz-conf-spjmpp/machines/capz-conf-spjmpp-md-win-67dbc9c465-pf947/crashdumps.tar
Nov 16 20:41:42.734: INFO: Collecting boot logs for AzureMachine capz-conf-spjmpp-md-win-x9q7m
�[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 4181 0 --:--:-- --:--:-- --:--:-- 4181 100 33 100 33 0 0 323 0 --:--:-- --:--:-- --:--:-- 323 100 33 100 33 0 0 323 0 --:--:-- --:--:-- --:--:-- 0 Error response from daemon: manifest for capzci.azurecr.io/kube-apiserver:v1.27.0-alpha.0.34_e4fc500f3ca85b not found: manifest unknown: manifest tagged by "v1.27.0-alpha.0.34_e4fc500f3ca85b" is not found Building Kubernetes make: Entering directory '/home/prow/go/src/k8s.io/kubernetes' +++ [1116 19:32:36] Verifying Prerequisites.... +++ [1116 19:32:36] Building Docker image kube-build:build-9d94cb6b4e-5-v1.25.0-go1.19.3-bullseye.0 +++ [1116 19:36:33] Creating data container kube-build-data-9d94cb6b4e-5-v1.25.0-go1.19.3-bullseye.0 +++ [1116 19:36:58] Syncing sources to container ... skipping 750 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-spjmpp [1mSTEP[0m: Creating namespace "capz-conf-spjmpp" for hosting the cluster Nov 16 20:19:47.069: INFO: starting to create namespace for hosting the "capz-conf-spjmpp" test spec 2022/11/16 20:19:47 failed trying to get namespace (capz-conf-spjmpp):namespaces "capz-conf-spjmpp" not found INFO: Creating namespace capz-conf-spjmpp INFO: Creating event watcher for namespace "capz-conf-spjmpp" [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-spjmpp" using the "conformance-presubmit-artifacts-windows-containerd" template (Kubernetes v1.27.0-alpha.0.26+43b7a253539a77, 1 control-plane machines, 0 worker machines) INFO: Getting the cluster template yaml ... skipping 41 lines ... ==================================================== Random Seed: [1m1668630522[0m - will randomize all specs Will run [1m339[0m of [1m7073[0m specs Running in parallel across [1m4[0m processes [38;5;243m------------------------------[0m [38;5;9m[SynchronizedBeforeSuite] [FAILED] [606.179 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 16 20:28:43.445: INFO: >>> kubeConfig: /tmp/kubeconfig Nov 16 20:28:43.446: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable Nov 16 20:28:43.648: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready Nov 16 20:28:43.784: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:43.784: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:43.784: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:43.784: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) Nov 16 20:28:43.784: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:28:43.784: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:28:43.784: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:43.784: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:43.784: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:43.784: INFO: Nov 16 20:28:45.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:45.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:45.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:45.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (2 seconds elapsed) Nov 16 20:28:45.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:28:45.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:28:45.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:45.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:45.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:45.913: INFO: Nov 16 20:28:47.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:47.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:47.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:47.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (4 seconds elapsed) Nov 16 20:28:47.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:28:47.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:28:47.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:47.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:47.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:47.911: INFO: Nov 16 20:28:49.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:49.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:49.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:49.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (6 seconds elapsed) Nov 16 20:28:49.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:28:49.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:28:49.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:49.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:49.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:49.917: INFO: Nov 16 20:28:51.911: INFO: The status of Pod calico-node-windows-fl2zr is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:51.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:51.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:51.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:51.911: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (8 seconds elapsed) Nov 16 20:28:51.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:28:51.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:28:51.911: INFO: calico-node-windows-fl2zr capz-conf-x9q7m Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:58 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:50 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:50 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }] Nov 16 20:28:51.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:51.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:51.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:51.911: INFO: Nov 16 20:28:53.917: INFO: The status of Pod calico-node-windows-fl2zr is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:53.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:53.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:53.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:53.917: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (10 seconds elapsed) Nov 16 20:28:53.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:28:53.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:28:53.917: INFO: calico-node-windows-fl2zr capz-conf-x9q7m Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:58 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:50 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:50 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }] Nov 16 20:28:53.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:53.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:53.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:53.917: INFO: Nov 16 20:28:55.915: INFO: The status of Pod calico-node-windows-fl2zr is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:55.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:55.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:55.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:55.915: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (12 seconds elapsed) Nov 16 20:28:55.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:28:55.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:28:55.915: INFO: calico-node-windows-fl2zr capz-conf-x9q7m Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:58 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:50 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:50 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }] Nov 16 20:28:55.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:55.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:55.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:55.915: INFO: Nov 16 20:28:57.915: INFO: The status of Pod calico-node-windows-fl2zr is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:57.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:57.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:57.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:57.915: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (14 seconds elapsed) Nov 16 20:28:57.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:28:57.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:28:57.915: INFO: calico-node-windows-fl2zr capz-conf-x9q7m Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:58 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:50 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:50 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }] Nov 16 20:28:57.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:57.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:57.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:57.915: INFO: Nov 16 20:28:59.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:59.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:59.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:28:59.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (16 seconds elapsed) Nov 16 20:28:59.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:28:59.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:28:59.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:59.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:59.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:28:59.915: INFO: Nov 16 20:29:01.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:01.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:01.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:01.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (18 seconds elapsed) Nov 16 20:29:01.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:01.910: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:01.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:01.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:01.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:01.910: INFO: Nov 16 20:29:03.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:03.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:03.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:03.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (20 seconds elapsed) Nov 16 20:29:03.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:03.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:03.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:03.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:03.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:03.915: INFO: Nov 16 20:29:05.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:05.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:05.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:05.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (22 seconds elapsed) Nov 16 20:29:05.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:05.920: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:05.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:05.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:05.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:05.920: INFO: Nov 16 20:29:07.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:07.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:07.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:07.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (24 seconds elapsed) Nov 16 20:29:07.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:07.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:07.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:07.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:07.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:07.915: INFO: Nov 16 20:29:09.917: INFO: The status of Pod calico-node-windows-rqv4b is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:09.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:09.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:09.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:09.917: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (26 seconds elapsed) Nov 16 20:29:09.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:09.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:09.917: INFO: calico-node-windows-rqv4b capz-conf-mq8ck Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:22 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:29:08 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:29:08 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }] Nov 16 20:29:09.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:09.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:09.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:09.917: INFO: Nov 16 20:29:11.917: INFO: The status of Pod calico-node-windows-rqv4b is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:11.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:11.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:11.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:11.917: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (28 seconds elapsed) Nov 16 20:29:11.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:11.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:11.917: INFO: calico-node-windows-rqv4b capz-conf-mq8ck Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:22 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:29:08 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:29:08 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }] Nov 16 20:29:11.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:11.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:11.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:11.917: INFO: Nov 16 20:29:13.915: INFO: The status of Pod calico-node-windows-rqv4b is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:13.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:13.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:13.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:13.915: INFO: 14 / 18 pods in namespace 'kube-system' are running and ready (30 seconds elapsed) Nov 16 20:29:13.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:13.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:13.915: INFO: calico-node-windows-rqv4b capz-conf-mq8ck Running [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:28:22 +0000 UTC } {Ready False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:29:08 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:29:08 +0000 UTC ContainersNotReady containers with unready status: [calico-node-felix]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2022-11-16 20:27:29 +0000 UTC }] Nov 16 20:29:13.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:13.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:13.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:13.915: INFO: Nov 16 20:29:15.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:15.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:15.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:15.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (32 seconds elapsed) Nov 16 20:29:15.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:15.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:15.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:15.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:15.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:15.914: INFO: Nov 16 20:29:17.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:17.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:17.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:17.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (34 seconds elapsed) Nov 16 20:29:17.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:17.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:17.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:17.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:17.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:17.915: INFO: Nov 16 20:29:19.921: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:19.921: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:19.921: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:19.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (36 seconds elapsed) Nov 16 20:29:19.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:19.921: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:19.921: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:19.921: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:19.921: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:19.921: INFO: Nov 16 20:29:21.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:21.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:21.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:21.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (38 seconds elapsed) Nov 16 20:29:21.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:21.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:21.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:21.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:21.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:21.915: INFO: Nov 16 20:29:23.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:23.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:23.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:23.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (40 seconds elapsed) Nov 16 20:29:23.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:23.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:23.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:23.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:23.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:23.911: INFO: Nov 16 20:29:25.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:25.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:25.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:25.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (42 seconds elapsed) Nov 16 20:29:25.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:25.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:25.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:25.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:25.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:25.913: INFO: Nov 16 20:29:27.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:27.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:27.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:27.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (44 seconds elapsed) Nov 16 20:29:27.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:27.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:27.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:27.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:27.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:27.912: INFO: Nov 16 20:29:29.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:29.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:29.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:29.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (46 seconds elapsed) Nov 16 20:29:29.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:29.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:29.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:29.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:29.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:29.913: INFO: Nov 16 20:29:31.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:31.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:31.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:31.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (48 seconds elapsed) Nov 16 20:29:31.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:31.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:31.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:31.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:31.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:31.914: INFO: Nov 16 20:29:33.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:33.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:33.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:33.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (50 seconds elapsed) Nov 16 20:29:33.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:33.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:33.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:33.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:33.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:33.912: INFO: Nov 16 20:29:35.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:35.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:35.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:35.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (52 seconds elapsed) Nov 16 20:29:35.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:35.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:35.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:35.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:35.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:35.914: INFO: Nov 16 20:29:37.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:37.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:37.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:37.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (54 seconds elapsed) Nov 16 20:29:37.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:37.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:37.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:37.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:37.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:37.914: INFO: Nov 16 20:29:39.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:39.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:39.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:39.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (56 seconds elapsed) Nov 16 20:29:39.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:39.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:39.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:39.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:39.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:39.915: INFO: Nov 16 20:29:41.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:41.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:41.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:41.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (58 seconds elapsed) Nov 16 20:29:41.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:41.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:41.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:41.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:41.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:41.913: INFO: Nov 16 20:29:43.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:43.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:43.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:43.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (60 seconds elapsed) Nov 16 20:29:43.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:43.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:43.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:43.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:43.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:43.912: INFO: Nov 16 20:29:45.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:45.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:45.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:45.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (62 seconds elapsed) Nov 16 20:29:45.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:45.920: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:45.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:45.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:45.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:45.920: INFO: Nov 16 20:29:47.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:47.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:47.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:47.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (64 seconds elapsed) Nov 16 20:29:47.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:47.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:47.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:47.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:47.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:47.911: INFO: Nov 16 20:29:49.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:49.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:49.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:49.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (66 seconds elapsed) Nov 16 20:29:49.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:49.910: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:49.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:49.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:49.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:49.910: INFO: Nov 16 20:29:51.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:51.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:51.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:51.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (68 seconds elapsed) Nov 16 20:29:51.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:51.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:51.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:51.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:51.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:51.913: INFO: Nov 16 20:29:53.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:53.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:53.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:53.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (70 seconds elapsed) Nov 16 20:29:53.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:53.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:53.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:53.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:53.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:53.912: INFO: Nov 16 20:29:55.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:55.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:55.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:55.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (72 seconds elapsed) Nov 16 20:29:55.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:55.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:55.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:55.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:55.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:55.913: INFO: Nov 16 20:29:57.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:57.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:57.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:57.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (74 seconds elapsed) Nov 16 20:29:57.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:57.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:57.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:57.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:57.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:57.912: INFO: Nov 16 20:29:59.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:59.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:59.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:29:59.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (76 seconds elapsed) Nov 16 20:29:59.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:29:59.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:29:59.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:59.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:59.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:29:59.915: INFO: Nov 16 20:30:01.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:01.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:01.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:01.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (78 seconds elapsed) Nov 16 20:30:01.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:01.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:01.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:01.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:01.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:01.913: INFO: Nov 16 20:30:03.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:03.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:03.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:03.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (80 seconds elapsed) Nov 16 20:30:03.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:03.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:03.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:03.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:03.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:03.913: INFO: Nov 16 20:30:05.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:05.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:05.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:05.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (82 seconds elapsed) Nov 16 20:30:05.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:05.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:05.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:05.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:05.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:05.914: INFO: Nov 16 20:30:07.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:07.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:07.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:07.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (84 seconds elapsed) Nov 16 20:30:07.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:07.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:07.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:07.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:07.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:07.916: INFO: Nov 16 20:30:09.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:09.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:09.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:09.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (86 seconds elapsed) Nov 16 20:30:09.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:09.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:09.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:09.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:09.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:09.916: INFO: Nov 16 20:30:11.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:11.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:11.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:11.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (88 seconds elapsed) Nov 16 20:30:11.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:11.919: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:11.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:11.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:11.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:11.920: INFO: Nov 16 20:30:13.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:13.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:13.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:13.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (90 seconds elapsed) Nov 16 20:30:13.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:13.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:13.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:13.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:13.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:13.913: INFO: Nov 16 20:30:15.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:15.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:15.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:15.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (92 seconds elapsed) Nov 16 20:30:15.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:15.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:15.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:15.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:15.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:15.912: INFO: Nov 16 20:30:17.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:17.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:17.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:17.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (94 seconds elapsed) Nov 16 20:30:17.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:17.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:17.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:17.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:17.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:17.913: INFO: Nov 16 20:30:19.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:19.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:19.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:19.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (96 seconds elapsed) Nov 16 20:30:19.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:19.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:19.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:19.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:19.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:19.913: INFO: Nov 16 20:30:22.022: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:22.022: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:22.022: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:22.022: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (98 seconds elapsed) Nov 16 20:30:22.022: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:22.022: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:22.022: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:22.022: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:22.022: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:22.022: INFO: Nov 16 20:30:23.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:23.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:23.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:23.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (100 seconds elapsed) Nov 16 20:30:23.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:23.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:23.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:23.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:23.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:23.911: INFO: Nov 16 20:30:25.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:25.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:25.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:25.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (102 seconds elapsed) Nov 16 20:30:25.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:25.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:25.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:25.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:25.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:25.911: INFO: Nov 16 20:30:27.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:27.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:27.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:27.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (104 seconds elapsed) Nov 16 20:30:27.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:27.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:27.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:27.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:27.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:27.913: INFO: Nov 16 20:30:29.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:29.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:29.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:29.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (106 seconds elapsed) Nov 16 20:30:29.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:29.910: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:29.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:29.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:29.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:29.910: INFO: Nov 16 20:30:31.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:31.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:31.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:31.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (108 seconds elapsed) Nov 16 20:30:31.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:31.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:31.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:31.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:31.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:31.911: INFO: Nov 16 20:30:33.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:33.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:33.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:33.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (110 seconds elapsed) Nov 16 20:30:33.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:33.918: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:33.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:33.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:33.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:33.918: INFO: Nov 16 20:30:35.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:35.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:35.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:35.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (112 seconds elapsed) Nov 16 20:30:35.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:35.918: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:35.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:35.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:35.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:35.918: INFO: Nov 16 20:30:37.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:37.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:37.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:37.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (114 seconds elapsed) Nov 16 20:30:37.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:37.910: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:37.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:37.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:37.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:37.910: INFO: Nov 16 20:30:39.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:39.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:39.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:39.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (116 seconds elapsed) Nov 16 20:30:39.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:39.919: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:39.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:39.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:39.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:39.919: INFO: Nov 16 20:30:41.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:41.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:41.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:41.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (118 seconds elapsed) Nov 16 20:30:41.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:41.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:41.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:41.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:41.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:41.916: INFO: Nov 16 20:30:43.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:43.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:43.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:43.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (120 seconds elapsed) Nov 16 20:30:43.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:43.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:43.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:43.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:43.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:43.911: INFO: Nov 16 20:30:45.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:45.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:45.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:45.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (122 seconds elapsed) Nov 16 20:30:45.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:45.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:45.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:45.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:45.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:45.917: INFO: Nov 16 20:30:47.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:47.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:47.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:47.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (124 seconds elapsed) Nov 16 20:30:47.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:47.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:47.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:47.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:47.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:47.915: INFO: Nov 16 20:30:49.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:49.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:49.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:49.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (126 seconds elapsed) Nov 16 20:30:49.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:49.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:49.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:49.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:49.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:49.913: INFO: Nov 16 20:30:51.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:51.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:51.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:51.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (128 seconds elapsed) Nov 16 20:30:51.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:51.910: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:51.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:51.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:51.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:51.910: INFO: Nov 16 20:30:53.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:53.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:53.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:53.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (130 seconds elapsed) Nov 16 20:30:53.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:53.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:53.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:53.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:53.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:53.913: INFO: Nov 16 20:30:55.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:55.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:55.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:55.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (132 seconds elapsed) Nov 16 20:30:55.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:55.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:55.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:55.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:55.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:55.913: INFO: Nov 16 20:30:57.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:57.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:57.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:57.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (134 seconds elapsed) Nov 16 20:30:57.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:57.910: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:57.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:57.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:57.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:57.910: INFO: Nov 16 20:30:59.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:59.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:59.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:30:59.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (136 seconds elapsed) Nov 16 20:30:59.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:30:59.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:30:59.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:59.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:59.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:30:59.912: INFO: Nov 16 20:31:01.923: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:01.923: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:01.923: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:01.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (138 seconds elapsed) Nov 16 20:31:01.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:01.923: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:01.923: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:01.923: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:01.923: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:01.923: INFO: Nov 16 20:31:03.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:03.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:03.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:03.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (140 seconds elapsed) Nov 16 20:31:03.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:03.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:03.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:03.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:03.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:03.914: INFO: Nov 16 20:31:05.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:05.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:05.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:05.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (142 seconds elapsed) Nov 16 20:31:05.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:05.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:05.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:05.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:05.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:05.915: INFO: Nov 16 20:31:07.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:07.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:07.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:07.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (144 seconds elapsed) Nov 16 20:31:07.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:07.918: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:07.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:07.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:07.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:07.918: INFO: Nov 16 20:31:09.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:09.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:09.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:09.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (146 seconds elapsed) Nov 16 20:31:09.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:09.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:09.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:09.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:09.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:09.913: INFO: Nov 16 20:31:11.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:11.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:11.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:11.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (148 seconds elapsed) Nov 16 20:31:11.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:11.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:11.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:11.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:11.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:11.911: INFO: Nov 16 20:31:13.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:13.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:13.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:13.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (150 seconds elapsed) Nov 16 20:31:13.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:13.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:13.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:13.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:13.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:13.913: INFO: Nov 16 20:31:15.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:15.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:15.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:15.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (152 seconds elapsed) Nov 16 20:31:15.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:15.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:15.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:15.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:15.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:15.914: INFO: Nov 16 20:31:17.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:17.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:17.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:17.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (154 seconds elapsed) Nov 16 20:31:17.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:17.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:17.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:17.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:17.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:17.914: INFO: Nov 16 20:31:19.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:19.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:19.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:19.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (156 seconds elapsed) Nov 16 20:31:19.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:19.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:19.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:19.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:19.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:19.916: INFO: Nov 16 20:31:21.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:21.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:21.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:21.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (158 seconds elapsed) Nov 16 20:31:21.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:21.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:21.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:21.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:21.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:21.914: INFO: Nov 16 20:31:23.921: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:23.921: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:23.921: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:23.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (160 seconds elapsed) Nov 16 20:31:23.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:23.921: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:23.921: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:23.921: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:23.921: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:23.921: INFO: Nov 16 20:31:25.926: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:25.926: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:25.926: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:25.926: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (162 seconds elapsed) Nov 16 20:31:25.926: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:25.926: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:25.926: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:25.926: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:25.926: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:25.926: INFO: Nov 16 20:31:27.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:27.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:27.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:27.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (164 seconds elapsed) Nov 16 20:31:27.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:27.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:27.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:27.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:27.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:27.915: INFO: Nov 16 20:31:29.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:29.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:29.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:29.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (166 seconds elapsed) Nov 16 20:31:29.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:29.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:29.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:29.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:29.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:29.917: INFO: Nov 16 20:31:31.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:31.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:31.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:31.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (168 seconds elapsed) Nov 16 20:31:31.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:31.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:31.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:31.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:31.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:31.911: INFO: Nov 16 20:31:33.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:33.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:33.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:33.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (170 seconds elapsed) Nov 16 20:31:33.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:33.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:33.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:33.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:33.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:33.915: INFO: Nov 16 20:31:35.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:35.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:35.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:35.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (172 seconds elapsed) Nov 16 20:31:35.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:35.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:35.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:35.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:35.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:35.912: INFO: Nov 16 20:31:37.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:37.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:37.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:37.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (174 seconds elapsed) Nov 16 20:31:37.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:37.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:37.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:37.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:37.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:37.913: INFO: Nov 16 20:31:39.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:39.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:39.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:39.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (176 seconds elapsed) Nov 16 20:31:39.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:39.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:39.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:39.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:39.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:39.915: INFO: Nov 16 20:31:41.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:41.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:41.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:41.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (178 seconds elapsed) Nov 16 20:31:41.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:41.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:41.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:41.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:41.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:41.914: INFO: Nov 16 20:31:43.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:43.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:43.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:43.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (180 seconds elapsed) Nov 16 20:31:43.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:43.919: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:43.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:43.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:43.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:43.919: INFO: Nov 16 20:31:45.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:45.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:45.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:45.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (182 seconds elapsed) Nov 16 20:31:45.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:45.910: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:45.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:45.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:45.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:45.910: INFO: Nov 16 20:31:47.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:47.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:47.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:47.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (184 seconds elapsed) Nov 16 20:31:47.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:47.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:47.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:47.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:47.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:47.911: INFO: Nov 16 20:31:49.931: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:49.931: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:49.931: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:49.931: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (186 seconds elapsed) Nov 16 20:31:49.931: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:49.931: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:49.931: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:49.931: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:49.931: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:49.931: INFO: Nov 16 20:31:51.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:51.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:51.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:51.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (188 seconds elapsed) Nov 16 20:31:51.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:51.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:51.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:51.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:51.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:51.912: INFO: Nov 16 20:31:53.923: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:53.923: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:53.923: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:53.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (190 seconds elapsed) Nov 16 20:31:53.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:53.923: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:53.923: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:53.923: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:53.923: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:53.923: INFO: Nov 16 20:31:55.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:55.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:55.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:55.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (192 seconds elapsed) Nov 16 20:31:55.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:55.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:55.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:55.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:55.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:55.913: INFO: Nov 16 20:31:57.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:57.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:57.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:57.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (194 seconds elapsed) Nov 16 20:31:57.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:57.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:57.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:57.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:57.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:57.911: INFO: Nov 16 20:31:59.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:59.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:59.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:31:59.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (196 seconds elapsed) Nov 16 20:31:59.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:31:59.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:31:59.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:59.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:59.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:31:59.912: INFO: Nov 16 20:32:01.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:01.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:01.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:01.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (198 seconds elapsed) Nov 16 20:32:01.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:01.910: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:01.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:01.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:01.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:01.910: INFO: Nov 16 20:32:03.958: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:03.958: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:03.958: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:03.958: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (200 seconds elapsed) Nov 16 20:32:03.958: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:03.958: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:03.958: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:03.958: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:03.958: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:03.958: INFO: Nov 16 20:32:05.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:05.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:05.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:05.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (202 seconds elapsed) Nov 16 20:32:05.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:05.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:05.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:05.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:05.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:05.914: INFO: Nov 16 20:32:07.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:07.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:07.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:07.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (204 seconds elapsed) Nov 16 20:32:07.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:07.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:07.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:07.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:07.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:07.912: INFO: Nov 16 20:32:09.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:09.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:09.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:09.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (206 seconds elapsed) Nov 16 20:32:09.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:09.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:09.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:09.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:09.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:09.912: INFO: Nov 16 20:32:11.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:11.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:11.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:11.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (208 seconds elapsed) Nov 16 20:32:11.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:11.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:11.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:11.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:11.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:11.915: INFO: Nov 16 20:32:13.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:13.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:13.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:13.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (210 seconds elapsed) Nov 16 20:32:13.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:13.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:13.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:13.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:13.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:13.912: INFO: Nov 16 20:32:15.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:15.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:15.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:15.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (212 seconds elapsed) Nov 16 20:32:15.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:15.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:15.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:15.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:15.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:15.913: INFO: Nov 16 20:32:17.926: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:17.926: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:17.926: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:17.926: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (214 seconds elapsed) Nov 16 20:32:17.926: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:17.926: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:17.926: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:17.926: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:17.926: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:17.926: INFO: Nov 16 20:32:19.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:19.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:19.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:19.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (216 seconds elapsed) Nov 16 20:32:19.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:19.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:19.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:19.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:19.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:19.913: INFO: Nov 16 20:32:21.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:21.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:21.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:21.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (218 seconds elapsed) Nov 16 20:32:21.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:21.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:21.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:21.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:21.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:21.911: INFO: Nov 16 20:32:23.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:23.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:23.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:23.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (220 seconds elapsed) Nov 16 20:32:23.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:23.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:23.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:23.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:23.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:23.912: INFO: Nov 16 20:32:25.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:25.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:25.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:25.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (222 seconds elapsed) Nov 16 20:32:25.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:25.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:25.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:25.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:25.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:25.917: INFO: Nov 16 20:32:27.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:27.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:27.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:27.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (224 seconds elapsed) Nov 16 20:32:27.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:27.910: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:27.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:27.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:27.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:27.910: INFO: Nov 16 20:32:29.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:29.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:29.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:29.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (226 seconds elapsed) Nov 16 20:32:29.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:29.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:29.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:29.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:29.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:29.916: INFO: Nov 16 20:32:32.023: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:32.023: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:32.023: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:32.023: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (228 seconds elapsed) Nov 16 20:32:32.023: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:32.023: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:32.023: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:32.023: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:32.023: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:32.023: INFO: Nov 16 20:32:33.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:33.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:33.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:33.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (230 seconds elapsed) Nov 16 20:32:33.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:33.918: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:33.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:33.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:33.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:33.918: INFO: Nov 16 20:32:35.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:35.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:35.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:35.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (232 seconds elapsed) Nov 16 20:32:35.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:35.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:35.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:35.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:35.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:35.914: INFO: Nov 16 20:32:37.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:37.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:37.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:37.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (234 seconds elapsed) Nov 16 20:32:37.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:37.910: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:37.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:37.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:37.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:37.910: INFO: Nov 16 20:32:39.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:39.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:39.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:39.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (236 seconds elapsed) Nov 16 20:32:39.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:39.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:39.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:39.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:39.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:39.912: INFO: Nov 16 20:32:41.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:41.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:41.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:41.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (238 seconds elapsed) Nov 16 20:32:41.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:41.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:41.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:41.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:41.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:41.912: INFO: Nov 16 20:32:43.931: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:43.931: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:43.931: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:43.931: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (240 seconds elapsed) Nov 16 20:32:43.931: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:43.931: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:43.931: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:43.931: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:43.931: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:43.931: INFO: Nov 16 20:32:45.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:45.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:45.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:45.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (242 seconds elapsed) Nov 16 20:32:45.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:45.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:45.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:45.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:45.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:45.914: INFO: Nov 16 20:32:47.942: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:47.942: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:47.942: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:47.942: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (244 seconds elapsed) Nov 16 20:32:47.942: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:47.942: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:47.942: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:47.942: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:47.942: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:47.942: INFO: Nov 16 20:32:49.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:49.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:49.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:49.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (246 seconds elapsed) Nov 16 20:32:49.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:49.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:49.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:49.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:49.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:49.912: INFO: Nov 16 20:32:51.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:51.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:51.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:51.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (248 seconds elapsed) Nov 16 20:32:51.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:51.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:51.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:51.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:51.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:51.912: INFO: Nov 16 20:32:53.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:53.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:53.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:53.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (250 seconds elapsed) Nov 16 20:32:53.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:53.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:53.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:53.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:53.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:53.915: INFO: Nov 16 20:32:55.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:55.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:55.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:55.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (252 seconds elapsed) Nov 16 20:32:55.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:55.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:55.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:55.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:55.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:55.913: INFO: Nov 16 20:32:57.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:57.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:57.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:57.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (254 seconds elapsed) Nov 16 20:32:57.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:57.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:57.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:57.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:57.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:57.916: INFO: Nov 16 20:32:59.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:59.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:59.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:32:59.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (256 seconds elapsed) Nov 16 20:32:59.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:32:59.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:32:59.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:59.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:59.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:32:59.911: INFO: Nov 16 20:33:01.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:01.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:01.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:01.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (258 seconds elapsed) Nov 16 20:33:01.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:01.922: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:01.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:01.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:01.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:01.922: INFO: Nov 16 20:33:03.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:03.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:03.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:03.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (260 seconds elapsed) Nov 16 20:33:03.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:03.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:03.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:03.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:03.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:03.912: INFO: Nov 16 20:33:05.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:05.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:05.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:05.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (262 seconds elapsed) Nov 16 20:33:05.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:05.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:05.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:05.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:05.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:05.917: INFO: Nov 16 20:33:07.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:07.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:07.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:07.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (264 seconds elapsed) Nov 16 20:33:07.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:07.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:07.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:07.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:07.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:07.913: INFO: Nov 16 20:33:09.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:09.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:09.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:09.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (266 seconds elapsed) Nov 16 20:33:09.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:09.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:09.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:09.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:09.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:09.913: INFO: Nov 16 20:33:11.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:11.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:11.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:11.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (268 seconds elapsed) Nov 16 20:33:11.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:11.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:11.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:11.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:11.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:11.913: INFO: Nov 16 20:33:13.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:13.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:13.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:13.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (270 seconds elapsed) Nov 16 20:33:13.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:13.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:13.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:13.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:13.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:13.913: INFO: Nov 16 20:33:15.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:15.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:15.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:15.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (272 seconds elapsed) Nov 16 20:33:15.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:15.919: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:15.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:15.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:15.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:15.919: INFO: Nov 16 20:33:17.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:17.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:17.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:17.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (274 seconds elapsed) Nov 16 20:33:17.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:17.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:17.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:17.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:17.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:17.914: INFO: Nov 16 20:33:19.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:19.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:19.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:19.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (276 seconds elapsed) Nov 16 20:33:19.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:19.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:19.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:19.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:19.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:19.912: INFO: Nov 16 20:33:21.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:21.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:21.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:21.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (278 seconds elapsed) Nov 16 20:33:21.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:21.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:21.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:21.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:21.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:21.915: INFO: Nov 16 20:33:23.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:23.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:23.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:23.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (280 seconds elapsed) Nov 16 20:33:23.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:23.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:23.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:23.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:23.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:23.914: INFO: Nov 16 20:33:25.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:25.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:25.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:25.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (282 seconds elapsed) Nov 16 20:33:25.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:25.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:25.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:25.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:25.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:25.913: INFO: Nov 16 20:33:27.909: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:27.909: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:27.909: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:27.909: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (284 seconds elapsed) Nov 16 20:33:27.909: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:27.909: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:27.909: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:27.909: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:27.909: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:27.909: INFO: Nov 16 20:33:29.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:29.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:29.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:29.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (286 seconds elapsed) Nov 16 20:33:29.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:29.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:29.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:29.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:29.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:29.913: INFO: Nov 16 20:33:31.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:31.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:31.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:31.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (288 seconds elapsed) Nov 16 20:33:31.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:31.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:31.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:31.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:31.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:31.913: INFO: Nov 16 20:33:33.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:33.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:33.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:33.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (290 seconds elapsed) Nov 16 20:33:33.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:33.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:33.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:33.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:33.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:33.911: INFO: Nov 16 20:33:35.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:35.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:35.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:35.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (292 seconds elapsed) Nov 16 20:33:35.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:35.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:35.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:35.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:35.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:35.915: INFO: Nov 16 20:33:37.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:37.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:37.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:37.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (294 seconds elapsed) Nov 16 20:33:37.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:37.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:37.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:37.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:37.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:37.914: INFO: Nov 16 20:33:39.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:39.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:39.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:39.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (296 seconds elapsed) Nov 16 20:33:39.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:39.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:39.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:39.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:39.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:39.911: INFO: Nov 16 20:33:41.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:41.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:41.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:41.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (298 seconds elapsed) Nov 16 20:33:41.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:41.910: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:41.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:41.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:41.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:41.910: INFO: Nov 16 20:33:43.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:43.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:43.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:43.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (300 seconds elapsed) Nov 16 20:33:43.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:43.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:43.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:43.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:43.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:43.914: INFO: Nov 16 20:33:45.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:45.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:45.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:45.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (302 seconds elapsed) Nov 16 20:33:45.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:45.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:45.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:45.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:45.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:45.914: INFO: Nov 16 20:33:47.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:47.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:47.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:47.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (304 seconds elapsed) Nov 16 20:33:47.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:47.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:47.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:47.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:47.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:47.914: INFO: Nov 16 20:33:49.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:49.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:49.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:49.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (306 seconds elapsed) Nov 16 20:33:49.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:49.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:49.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:49.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:49.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:49.912: INFO: Nov 16 20:33:51.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:51.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:51.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:51.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (308 seconds elapsed) Nov 16 20:33:51.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:51.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:51.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:51.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:51.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:51.912: INFO: Nov 16 20:33:53.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:53.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:53.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:53.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (310 seconds elapsed) Nov 16 20:33:53.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:53.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:53.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:53.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:53.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:53.916: INFO: Nov 16 20:33:55.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:55.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:55.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:55.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (312 seconds elapsed) Nov 16 20:33:55.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:55.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:55.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:55.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:55.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:55.911: INFO: Nov 16 20:33:57.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:57.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:57.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:57.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (314 seconds elapsed) Nov 16 20:33:57.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:57.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:57.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:57.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:57.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:57.914: INFO: Nov 16 20:33:59.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:59.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:59.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:33:59.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (316 seconds elapsed) Nov 16 20:33:59.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:33:59.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:33:59.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:59.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:59.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:33:59.912: INFO: Nov 16 20:34:01.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:01.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:01.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:01.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (318 seconds elapsed) Nov 16 20:34:01.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:01.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:01.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:01.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:01.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:01.913: INFO: Nov 16 20:34:03.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:03.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:03.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:03.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (320 seconds elapsed) Nov 16 20:34:03.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:03.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:03.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:03.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:03.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:03.912: INFO: Nov 16 20:34:05.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:05.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:05.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:05.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (322 seconds elapsed) Nov 16 20:34:05.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:05.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:05.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:05.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:05.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:05.913: INFO: Nov 16 20:34:07.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:07.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:07.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:07.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (324 seconds elapsed) Nov 16 20:34:07.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:07.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:07.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:07.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:07.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:07.911: INFO: Nov 16 20:34:09.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:09.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:09.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:09.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (326 seconds elapsed) Nov 16 20:34:09.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:09.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:09.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:09.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:09.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:09.911: INFO: Nov 16 20:34:11.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:11.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:11.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:11.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (328 seconds elapsed) Nov 16 20:34:11.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:11.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:11.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:11.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:11.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:11.911: INFO: Nov 16 20:34:13.926: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:13.926: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:13.926: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:13.926: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (330 seconds elapsed) Nov 16 20:34:13.926: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:13.926: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:13.926: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:13.926: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:13.926: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:13.926: INFO: Nov 16 20:34:15.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:15.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:15.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:15.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (332 seconds elapsed) Nov 16 20:34:15.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:15.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:15.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:15.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:15.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:15.915: INFO: Nov 16 20:34:17.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:17.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:17.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:17.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (334 seconds elapsed) Nov 16 20:34:17.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:17.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:17.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:17.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:17.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:17.912: INFO: Nov 16 20:34:19.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:19.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:19.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:19.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (336 seconds elapsed) Nov 16 20:34:19.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:19.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:19.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:19.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:19.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:19.917: INFO: Nov 16 20:34:21.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:21.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:21.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:21.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (338 seconds elapsed) Nov 16 20:34:21.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:21.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:21.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:21.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:21.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:21.917: INFO: Nov 16 20:34:23.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:23.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:23.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:23.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (340 seconds elapsed) Nov 16 20:34:23.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:23.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:23.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:23.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:23.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:23.913: INFO: Nov 16 20:34:25.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:25.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:25.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:25.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (342 seconds elapsed) Nov 16 20:34:25.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:25.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:25.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:25.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:25.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:25.913: INFO: Nov 16 20:34:27.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:27.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:27.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:27.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (344 seconds elapsed) Nov 16 20:34:27.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:27.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:27.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:27.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:27.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:27.914: INFO: Nov 16 20:34:29.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:29.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:29.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:29.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (346 seconds elapsed) Nov 16 20:34:29.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:29.910: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:29.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:29.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:29.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:29.910: INFO: Nov 16 20:34:31.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:31.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:31.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:31.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (348 seconds elapsed) Nov 16 20:34:31.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:31.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:31.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:31.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:31.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:31.911: INFO: Nov 16 20:34:33.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:33.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:33.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:33.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (350 seconds elapsed) Nov 16 20:34:33.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:33.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:33.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:33.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:33.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:33.912: INFO: Nov 16 20:34:35.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:35.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:35.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:35.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (352 seconds elapsed) Nov 16 20:34:35.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:35.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:35.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:35.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:35.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:35.913: INFO: Nov 16 20:34:37.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:37.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:37.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:37.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (354 seconds elapsed) Nov 16 20:34:37.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:37.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:37.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:37.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:37.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:37.914: INFO: Nov 16 20:34:39.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:39.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:39.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:39.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (356 seconds elapsed) Nov 16 20:34:39.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:39.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:39.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:39.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:39.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:39.912: INFO: Nov 16 20:34:41.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:41.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:41.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:41.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (358 seconds elapsed) Nov 16 20:34:41.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:41.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:41.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:41.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:41.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:41.912: INFO: Nov 16 20:34:43.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:43.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:43.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:43.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (360 seconds elapsed) Nov 16 20:34:43.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:43.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:43.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:43.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:43.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:43.912: INFO: Nov 16 20:34:45.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:45.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:45.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:45.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (362 seconds elapsed) Nov 16 20:34:45.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:45.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:45.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:45.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:45.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:45.916: INFO: Nov 16 20:34:47.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:47.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:47.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:47.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (364 seconds elapsed) Nov 16 20:34:47.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:47.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:47.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:47.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:47.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:47.915: INFO: Nov 16 20:34:49.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:49.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:49.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:49.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (366 seconds elapsed) Nov 16 20:34:49.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:49.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:49.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:49.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:49.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:49.912: INFO: Nov 16 20:34:51.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:51.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:51.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:51.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (368 seconds elapsed) Nov 16 20:34:51.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:51.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:51.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:51.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:51.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:51.913: INFO: Nov 16 20:34:53.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:53.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:53.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:53.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (370 seconds elapsed) Nov 16 20:34:53.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:53.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:53.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:53.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:53.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:53.915: INFO: Nov 16 20:34:55.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:55.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:55.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:55.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (372 seconds elapsed) Nov 16 20:34:55.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:55.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:55.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:55.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:55.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:55.915: INFO: Nov 16 20:34:57.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:57.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:57.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:57.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (374 seconds elapsed) Nov 16 20:34:57.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:57.910: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:57.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:57.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:57.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:57.910: INFO: Nov 16 20:34:59.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:59.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:59.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:34:59.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (376 seconds elapsed) Nov 16 20:34:59.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:34:59.910: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:34:59.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:59.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:59.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:34:59.910: INFO: Nov 16 20:35:01.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:01.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:01.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:01.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (378 seconds elapsed) Nov 16 20:35:01.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:01.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:01.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:01.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:01.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:01.914: INFO: Nov 16 20:35:03.921: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:03.921: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:03.921: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:03.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (380 seconds elapsed) Nov 16 20:35:03.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:03.921: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:03.921: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:03.921: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:03.921: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:03.921: INFO: Nov 16 20:35:05.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:05.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:05.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:05.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (382 seconds elapsed) Nov 16 20:35:05.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:05.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:05.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:05.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:05.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:05.913: INFO: Nov 16 20:35:07.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:07.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:07.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:07.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (384 seconds elapsed) Nov 16 20:35:07.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:07.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:07.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:07.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:07.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:07.911: INFO: Nov 16 20:35:09.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:09.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:09.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:09.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (386 seconds elapsed) Nov 16 20:35:09.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:09.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:09.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:09.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:09.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:09.913: INFO: Nov 16 20:35:11.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:11.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:11.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:11.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (388 seconds elapsed) Nov 16 20:35:11.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:11.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:11.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:11.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:11.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:11.911: INFO: Nov 16 20:35:13.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:13.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:13.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:13.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (390 seconds elapsed) Nov 16 20:35:13.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:13.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:13.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:13.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:13.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:13.912: INFO: Nov 16 20:35:15.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:15.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:15.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:15.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (392 seconds elapsed) Nov 16 20:35:15.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:15.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:15.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:15.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:15.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:15.911: INFO: Nov 16 20:35:17.910: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:17.910: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:17.910: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:17.910: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (394 seconds elapsed) Nov 16 20:35:17.910: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:17.910: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:17.910: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:17.910: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:17.910: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:17.910: INFO: Nov 16 20:35:19.911: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:19.911: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:19.911: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:19.911: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (396 seconds elapsed) Nov 16 20:35:19.911: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:19.911: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:19.911: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:19.911: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:19.911: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:19.911: INFO: Nov 16 20:35:21.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:21.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:21.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:21.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (398 seconds elapsed) Nov 16 20:35:21.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:21.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:21.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:21.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:21.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:21.912: INFO: Nov 16 20:35:23.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:23.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:23.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:23.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (400 seconds elapsed) Nov 16 20:35:23.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:23.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:23.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:23.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:23.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:23.913: INFO: Nov 16 20:35:25.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:25.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:25.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:25.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (402 seconds elapsed) Nov 16 20:35:25.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:25.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:25.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:25.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:25.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:25.915: INFO: Nov 16 20:35:27.912: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:27.912: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:27.912: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:27.912: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (404 seconds elapsed) Nov 16 20:35:27.912: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:27.912: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:27.912: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:27.912: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:27.912: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:27.912: INFO: Nov 16 20:35:29.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:29.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:29.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:29.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (406 seconds elapsed) Nov 16 20:35:29.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:29.918: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:29.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:29.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:29.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:29.918: INFO: Nov 16 20:35:31.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:31.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:31.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:31.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (408 seconds elapsed) Nov 16 20:35:31.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:31.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:31.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:31.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:31.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:31.913: INFO: Nov 16 20:35:33.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:33.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:33.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:33.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (410 seconds elapsed) Nov 16 20:35:33.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:33.919: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:33.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:33.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:33.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:33.919: INFO: Nov 16 20:35:35.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:35.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:35.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:35.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (412 seconds elapsed) Nov 16 20:35:35.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:35.918: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:35.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:35.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:35.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:35.918: INFO: Nov 16 20:35:37.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:37.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:37.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:37.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (414 seconds elapsed) Nov 16 20:35:37.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:37.919: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:37.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:37.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:37.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:37.919: INFO: Nov 16 20:35:39.923: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:39.923: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:39.923: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:39.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (416 seconds elapsed) Nov 16 20:35:39.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:39.923: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:39.923: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:39.923: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:39.923: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:39.923: INFO: Nov 16 20:35:41.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:41.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:41.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:41.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (418 seconds elapsed) Nov 16 20:35:41.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:41.918: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:41.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:41.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:41.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:41.918: INFO: Nov 16 20:35:43.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:43.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:43.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:43.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (420 seconds elapsed) Nov 16 20:35:43.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:43.918: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:43.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:43.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:43.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:43.918: INFO: Nov 16 20:35:45.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:45.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:45.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:45.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (422 seconds elapsed) Nov 16 20:35:45.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:45.922: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:45.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:45.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:45.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:45.922: INFO: Nov 16 20:35:48.030: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:48.030: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:48.030: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:48.030: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (424 seconds elapsed) Nov 16 20:35:48.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:48.030: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:48.030: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:48.030: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:48.030: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:48.030: INFO: Nov 16 20:35:49.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:49.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:49.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:49.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (426 seconds elapsed) Nov 16 20:35:49.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:49.922: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:49.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:49.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:49.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:49.922: INFO: Nov 16 20:35:51.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:51.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:51.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:51.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (428 seconds elapsed) Nov 16 20:35:51.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:51.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:51.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:51.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:51.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:51.915: INFO: Nov 16 20:35:53.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:53.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:53.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:53.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (430 seconds elapsed) Nov 16 20:35:53.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:53.919: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:53.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:53.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:53.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:53.919: INFO: Nov 16 20:35:55.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:55.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:55.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:55.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (432 seconds elapsed) Nov 16 20:35:55.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:55.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:55.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:55.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:55.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:55.916: INFO: Nov 16 20:35:57.930: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:57.930: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:57.930: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:57.930: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (434 seconds elapsed) Nov 16 20:35:57.930: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:57.930: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:57.930: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:57.930: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:57.930: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:57.930: INFO: Nov 16 20:35:59.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:59.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:59.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:35:59.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (436 seconds elapsed) Nov 16 20:35:59.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:35:59.919: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:35:59.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:59.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:59.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:35:59.919: INFO: Nov 16 20:36:01.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:01.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:01.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:01.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (438 seconds elapsed) Nov 16 20:36:01.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:01.919: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:01.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:01.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:01.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:01.919: INFO: Nov 16 20:36:03.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:03.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:03.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:03.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (440 seconds elapsed) Nov 16 20:36:03.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:03.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:03.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:03.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:03.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:03.917: INFO: Nov 16 20:36:05.927: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:05.927: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:05.927: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:05.928: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (442 seconds elapsed) Nov 16 20:36:05.928: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:05.928: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:05.928: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:05.928: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:05.928: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:05.928: INFO: Nov 16 20:36:07.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:07.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:07.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:07.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (444 seconds elapsed) Nov 16 20:36:07.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:07.919: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:07.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:07.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:07.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:07.919: INFO: Nov 16 20:36:09.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:09.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:09.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:09.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (446 seconds elapsed) Nov 16 20:36:09.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:09.918: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:09.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:09.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:09.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:09.918: INFO: Nov 16 20:36:11.924: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:11.924: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:11.924: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:11.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (448 seconds elapsed) Nov 16 20:36:11.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:11.924: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:11.924: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:11.924: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:11.924: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:11.924: INFO: Nov 16 20:36:13.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:13.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:13.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:13.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (450 seconds elapsed) Nov 16 20:36:13.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:13.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:13.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:13.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:13.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:13.913: INFO: Nov 16 20:36:15.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:15.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:15.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:15.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (452 seconds elapsed) Nov 16 20:36:15.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:15.922: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:15.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:15.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:15.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:15.922: INFO: Nov 16 20:36:17.928: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:17.928: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:17.928: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:17.928: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (454 seconds elapsed) Nov 16 20:36:17.928: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:17.928: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:17.928: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:17.928: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:17.928: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:17.928: INFO: Nov 16 20:36:19.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:19.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:19.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:19.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (456 seconds elapsed) Nov 16 20:36:19.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:19.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:19.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:19.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:19.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:19.917: INFO: Nov 16 20:36:21.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:21.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:21.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:21.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (458 seconds elapsed) Nov 16 20:36:21.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:21.920: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:21.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:21.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:21.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:21.920: INFO: Nov 16 20:36:24.032: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:24.032: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:24.032: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:24.032: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (460 seconds elapsed) Nov 16 20:36:24.032: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:24.032: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:24.032: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:24.032: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:24.032: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:24.032: INFO: Nov 16 20:36:25.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:25.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:25.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:25.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (462 seconds elapsed) Nov 16 20:36:25.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:25.922: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:25.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:25.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:25.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:25.922: INFO: Nov 16 20:36:27.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:27.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:27.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:27.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (464 seconds elapsed) Nov 16 20:36:27.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:27.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:27.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:27.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:27.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:27.917: INFO: Nov 16 20:36:29.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:29.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:29.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:29.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (466 seconds elapsed) Nov 16 20:36:29.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:29.919: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:29.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:29.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:29.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:29.919: INFO: Nov 16 20:36:31.924: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:31.924: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:31.924: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:31.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (468 seconds elapsed) Nov 16 20:36:31.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:31.924: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:31.924: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:31.924: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:31.924: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:31.924: INFO: Nov 16 20:36:33.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:33.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:33.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:33.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (470 seconds elapsed) Nov 16 20:36:33.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:33.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:33.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:33.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:33.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:33.915: INFO: Nov 16 20:36:35.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:35.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:35.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:35.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (472 seconds elapsed) Nov 16 20:36:35.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:35.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:35.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:35.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:35.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:35.916: INFO: Nov 16 20:36:37.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:37.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:37.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:37.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (474 seconds elapsed) Nov 16 20:36:37.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:37.920: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:37.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:37.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:37.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:37.920: INFO: Nov 16 20:36:39.927: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:39.927: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:39.927: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:39.927: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (476 seconds elapsed) Nov 16 20:36:39.927: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:39.927: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:39.927: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:39.927: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:39.927: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:39.927: INFO: Nov 16 20:36:41.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:41.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:41.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:41.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (478 seconds elapsed) Nov 16 20:36:41.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:41.922: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:41.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:41.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:41.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:41.922: INFO: Nov 16 20:36:43.926: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:43.926: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:43.926: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:43.926: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (480 seconds elapsed) Nov 16 20:36:43.926: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:43.926: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:43.926: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:43.926: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:43.926: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:43.926: INFO: Nov 16 20:36:45.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:45.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:45.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:45.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (482 seconds elapsed) Nov 16 20:36:45.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:45.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:45.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:45.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:45.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:45.917: INFO: Nov 16 20:36:48.030: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:48.030: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:48.030: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:48.030: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (484 seconds elapsed) Nov 16 20:36:48.030: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:48.030: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:48.030: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:48.030: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:48.030: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:48.030: INFO: Nov 16 20:36:49.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:49.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:49.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:49.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (486 seconds elapsed) Nov 16 20:36:49.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:49.922: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:49.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:49.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:49.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:49.922: INFO: Nov 16 20:36:51.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:51.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:51.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:51.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (488 seconds elapsed) Nov 16 20:36:51.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:51.919: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:51.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:51.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:51.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:51.919: INFO: Nov 16 20:36:53.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:53.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:53.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:53.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (490 seconds elapsed) Nov 16 20:36:53.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:53.918: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:53.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:53.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:53.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:53.918: INFO: Nov 16 20:36:55.925: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:55.925: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:55.925: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:55.925: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (492 seconds elapsed) Nov 16 20:36:55.925: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:55.925: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:55.925: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:55.925: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:55.925: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:55.925: INFO: Nov 16 20:36:57.921: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:57.921: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:57.921: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:57.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (494 seconds elapsed) Nov 16 20:36:57.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:57.921: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:57.921: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:57.921: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:57.921: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:57.921: INFO: Nov 16 20:36:59.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:59.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:59.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:36:59.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (496 seconds elapsed) Nov 16 20:36:59.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:36:59.919: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:36:59.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:59.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:59.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:36:59.919: INFO: Nov 16 20:37:01.913: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:01.913: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:01.913: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:01.913: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (498 seconds elapsed) Nov 16 20:37:01.913: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:01.913: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:01.913: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:01.913: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:01.913: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:01.913: INFO: Nov 16 20:37:03.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:03.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:03.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:03.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (500 seconds elapsed) Nov 16 20:37:03.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:03.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:03.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:03.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:03.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:03.916: INFO: Nov 16 20:37:05.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:05.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:05.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:05.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (502 seconds elapsed) Nov 16 20:37:05.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:05.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:05.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:05.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:05.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:05.916: INFO: Nov 16 20:37:07.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:07.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:07.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:07.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (504 seconds elapsed) Nov 16 20:37:07.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:07.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:07.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:07.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:07.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:07.915: INFO: Nov 16 20:37:09.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:09.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:09.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:09.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (506 seconds elapsed) Nov 16 20:37:09.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:09.919: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:09.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:09.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:09.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:09.919: INFO: Nov 16 20:37:11.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:11.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:11.915: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:11.915: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (508 seconds elapsed) Nov 16 20:37:11.915: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:11.915: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:11.915: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:11.915: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:11.915: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:11.915: INFO: Nov 16 20:37:13.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:13.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:13.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:13.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (510 seconds elapsed) Nov 16 20:37:13.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:13.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:13.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:13.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:13.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:13.916: INFO: Nov 16 20:37:15.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:15.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:15.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:15.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (512 seconds elapsed) Nov 16 20:37:15.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:15.922: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:15.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:15.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:15.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:15.922: INFO: Nov 16 20:37:17.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:17.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:17.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:17.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (514 seconds elapsed) Nov 16 20:37:17.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:17.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:17.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:17.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:17.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:17.916: INFO: Nov 16 20:37:19.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:19.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:19.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:19.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (516 seconds elapsed) Nov 16 20:37:19.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:19.920: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:19.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:19.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:19.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:19.920: INFO: Nov 16 20:37:21.919: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:21.919: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:21.919: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:21.919: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (518 seconds elapsed) Nov 16 20:37:21.919: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:21.919: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:21.919: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:21.919: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:21.919: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:21.919: INFO: Nov 16 20:37:23.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:23.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:23.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:23.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (520 seconds elapsed) Nov 16 20:37:23.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:23.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:23.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:23.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:23.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:23.914: INFO: Nov 16 20:37:25.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:25.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:25.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:25.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (522 seconds elapsed) Nov 16 20:37:25.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:25.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:25.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:25.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:25.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:25.917: INFO: Nov 16 20:37:27.921: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:27.921: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:27.921: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:27.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (524 seconds elapsed) Nov 16 20:37:27.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:27.922: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:27.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:27.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:27.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:27.922: INFO: Nov 16 20:37:29.914: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:29.914: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:29.914: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:29.914: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (526 seconds elapsed) Nov 16 20:37:29.914: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:29.914: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:29.914: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:29.914: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:29.914: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:29.914: INFO: Nov 16 20:37:31.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:31.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:31.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:31.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (528 seconds elapsed) Nov 16 20:37:31.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:31.920: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:31.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:31.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:31.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:31.920: INFO: Nov 16 20:37:33.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:33.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:33.922: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:33.922: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (530 seconds elapsed) Nov 16 20:37:33.922: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:33.922: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:33.922: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:33.922: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:33.922: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:33.922: INFO: Nov 16 20:37:35.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:35.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:35.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:35.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (532 seconds elapsed) Nov 16 20:37:35.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:35.918: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:35.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:35.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:35.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:35.918: INFO: Nov 16 20:37:37.915: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:37.915: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:37.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:37.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (534 seconds elapsed) Nov 16 20:37:37.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:37.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:37.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:37.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:37.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:37.916: INFO: Nov 16 20:37:39.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:39.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:39.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:39.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (536 seconds elapsed) Nov 16 20:37:39.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:39.920: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:39.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:39.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:39.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:39.920: INFO: Nov 16 20:37:44.007: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:44.007: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:44.007: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:44.007: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (540 seconds elapsed) Nov 16 20:37:44.007: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:44.007: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:44.007: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:44.007: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:44.007: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:44.007: INFO: Nov 16 20:37:45.923: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:45.923: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:45.923: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:45.923: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (542 seconds elapsed) Nov 16 20:37:45.923: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:45.923: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:45.923: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:45.923: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:45.923: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:45.923: INFO: Nov 16 20:37:47.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:47.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:47.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:47.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (544 seconds elapsed) Nov 16 20:37:47.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:47.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:47.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:47.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:47.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:47.916: INFO: Nov 16 20:37:49.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:49.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:49.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:49.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (546 seconds elapsed) Nov 16 20:37:49.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:49.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:49.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:49.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:49.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:49.917: INFO: Nov 16 20:37:51.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:51.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:51.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:51.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (548 seconds elapsed) Nov 16 20:37:51.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:51.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:51.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:51.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:51.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:51.916: INFO: Nov 16 20:37:53.933: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:53.933: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:53.933: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:53.933: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (550 seconds elapsed) Nov 16 20:37:53.933: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:53.933: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:53.933: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:53.933: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:53.933: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:53.933: INFO: Nov 16 20:37:55.921: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:55.921: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:55.921: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:55.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (552 seconds elapsed) Nov 16 20:37:55.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:55.921: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:55.921: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:55.921: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:55.921: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:55.921: INFO: Nov 16 20:37:57.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:57.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:57.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:57.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (554 seconds elapsed) Nov 16 20:37:57.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:57.920: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:57.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:57.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:57.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:57.920: INFO: Nov 16 20:37:59.920: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:59.920: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:59.920: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:37:59.920: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (556 seconds elapsed) Nov 16 20:37:59.920: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:37:59.920: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:37:59.920: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:59.920: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:59.920: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:37:59.920: INFO: Nov 16 20:38:01.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:01.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:01.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:01.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (558 seconds elapsed) Nov 16 20:38:01.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:01.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:01.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:01.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:01.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:01.916: INFO: Nov 16 20:38:03.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:03.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:03.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:03.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (560 seconds elapsed) Nov 16 20:38:03.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:03.918: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:03.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:03.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:03.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:03.918: INFO: Nov 16 20:38:05.925: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:05.925: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:05.925: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:05.925: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (562 seconds elapsed) Nov 16 20:38:05.925: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:05.925: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:05.925: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:05.925: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:05.925: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:05.925: INFO: Nov 16 20:38:07.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:07.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:07.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:07.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (564 seconds elapsed) Nov 16 20:38:07.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:07.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:07.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:07.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:07.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:07.917: INFO: Nov 16 20:38:09.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:09.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:09.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:09.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (566 seconds elapsed) Nov 16 20:38:09.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:09.918: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:09.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:09.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:09.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:09.918: INFO: Nov 16 20:38:11.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:11.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:11.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:11.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (568 seconds elapsed) Nov 16 20:38:11.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:11.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:11.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:11.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:11.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:11.917: INFO: Nov 16 20:38:13.921: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:13.921: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:13.921: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:13.921: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (570 seconds elapsed) Nov 16 20:38:13.921: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:13.921: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:13.921: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:13.921: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:13.921: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:13.921: INFO: Nov 16 20:38:15.924: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:15.924: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:15.924: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:15.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (572 seconds elapsed) Nov 16 20:38:15.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:15.924: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:15.924: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:15.924: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:15.924: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:15.924: INFO: Nov 16 20:38:17.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:17.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:17.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:17.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (574 seconds elapsed) Nov 16 20:38:17.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:17.918: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:17.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:17.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:17.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:17.918: INFO: Nov 16 20:38:19.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:19.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:19.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:19.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (576 seconds elapsed) Nov 16 20:38:19.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:19.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:19.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:19.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:19.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:19.916: INFO: Nov 16 20:38:21.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:21.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:21.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:21.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (578 seconds elapsed) Nov 16 20:38:21.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:21.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:21.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:21.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:21.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:21.917: INFO: Nov 16 20:38:23.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:23.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:23.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:23.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (580 seconds elapsed) Nov 16 20:38:23.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:23.918: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:23.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:23.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:23.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:23.918: INFO: Nov 16 20:38:25.924: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:25.924: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:25.924: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:25.924: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (582 seconds elapsed) Nov 16 20:38:25.924: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:25.924: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:25.924: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:25.924: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:25.924: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:25.924: INFO: Nov 16 20:38:27.931: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:27.931: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:27.931: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:27.931: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (584 seconds elapsed) Nov 16 20:38:27.931: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:27.931: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:27.931: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:27.931: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:27.931: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:27.931: INFO: Nov 16 20:38:29.916: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:29.916: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:29.916: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:29.916: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (586 seconds elapsed) Nov 16 20:38:29.916: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:29.916: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:29.916: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:29.916: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:29.916: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:29.916: INFO: Nov 16 20:38:31.918: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:31.918: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:31.918: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:31.918: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (588 seconds elapsed) Nov 16 20:38:31.918: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:31.918: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:31.918: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:31.918: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:31.918: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:31.918: INFO: Nov 16 20:38:33.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:33.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:33.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:33.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (590 seconds elapsed) Nov 16 20:38:33.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:33.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:33.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:33.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:33.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:33.917: INFO: Nov 16 20:38:35.917: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:35.917: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:35.917: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:35.917: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (592 seconds elapsed) Nov 16 20:38:35.917: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:35.917: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:35.917: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:35.917: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:35.917: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:35.917: INFO: Nov 16 20:38:37.925: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:37.925: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:37.925: INFO: The status of Pod kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:37.925: INFO: 15 / 18 pods in namespace 'kube-system' are running and ready (594 seconds elapsed) Nov 16 20:38:37.925: INFO: expected 4 pod replicas in namespace 'kube-system', 4 are Running and Ready. Nov 16 20:38:37.925: INFO: POD NODE PHASE GRACE CONDITIONS Nov 16 20:38:37.925: INFO: kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:37.925: INFO: kube-controller-manager-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:37.925: INFO: kube-scheduler-capz-conf-spjmpp-control-plane-kbwv8 capz-conf-spjmpp-control-plane-kbwv8 Pending [] Nov 16 20:38:37.925: INFO: Nov 16 20:38:39.922: INFO: The status of Pod kube-apiserver-capz-conf-spjmpp-control-plane-kbwv8 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed Nov 16 20:38:39.922: INFO: The status of Pod kube-controller-manager-capz-conf-spjmpp-control-plane-k